Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Jan 2018 09:38:16 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 225423] panic: softdep_deallocate_dependencies: dangling deps
Message-ID:  <bug-225423-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225423

            Bug ID: 225423
           Summary: panic: softdep_deallocate_dependencies: dangling deps
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: deepak.ukey@microsemi.com

We have SmartRAID controller on which We are testing below test case. With =
this
test I am facing kernel panic and dump is pointing towards some file system
functions on FreeBSD 11.=20

Test Case:=20
We have installed FreeBSD11  on drive attached to Microsemi storage control=
ler
connected to Supermicro X10 system. We created the partition using gpart on=
 the
logical volumes behind Microsemi storage controller and executed write
operation using dd command. During the write operation, We removed the logi=
cal
volume. The logical volume gets destroyed but We faced Kernel panic. Please
find the below crash dump. The same issue observed in FreeBSD 10 also.=20

-------------------------------------------------------------------------
g_vfs_done():da5p1[READ(offset=3D324971036672, length=3D32768)]error =3D 6
(da5:smartpqi0:0:5:0): Periph destroyed
fsync: giving up on dirty 0xfffff801058a2b10: tag devfs, type VCHR
    usecount 1, writecount 0, refcount 103 mountedhere 0xfffff80010e84c00
    flags (VI_DOOMED|VI_ACTIVE)
    v_object 0xfffff8010fa41960 ref 0 pages 817 cleanbuf 98 dirtybuf 2
    lock type devfs: EXCL by thread 0xfffff8000b000000 (pid 778, login, tid
100169)
               dev da5p1
panic: softdep_deallocate_dependencies: dangling deps
cpuid =3D 0
KDB: stack backtrace:
#0 0xffffffff80aada97 at kdb_backtrace+0x67
#1 0xffffffff80a6bb76 at vpanic+0x186
#2 0xffffffff80a6b9e3 at panic+0x43
#3 0xffffffff80d14646 at softdep_deallocate_dependencies+0x76
#4 0xffffffff80b09435 at brelse+0x165
#5 0xffffffff80b27551 at flushbuflist+0x131
#6 0xffffffff80b2700b at bufobj_invalbuf+0x9b
#7 0xffffffff80b2a10e at vgonel+0x17e
#8 0xffffffff80b2a720 at vgone+0x40
#9 0xffffffff80934968 at devfs_delete+0x1d8
#10 0xffffffff80934e3a at devfs_populate_loop+0x21a
#11 0xffffffff80934c0a at devfs_populate+0x2a
#12 0xffffffff80939e1b at devfs_populate_vp+0x9b
#13 0xffffffff80937e0c at devfs_lookup+0x2c
#14 0xffffffff8104b853 at VOP_LOOKUP_APV+0x83
#15 0xffffffff80b1d0c1 at lookup+0x701
#16 0xffffffff80b1c576 at namei+0x486
#17 0xffffffff80b331fa at kern_chflagsat+0x9a
----------------------------------------------------------------------------

Could you please help us to resolve this problem.=20

PS: If same test case is executed with FIO(without any partition), it runs
fine.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225423-8>