[Bug 204764] Filesystem deadlock, process in vodead state

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204764

            Bug ID: 204764
           Summary: Filesystem deadlock, process in vodead state
           Product: Base System
           Version: 10.2-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: rs at bytecamp.net

Created attachment 163453
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163453&action=edit
procstat -kk -a output

FreeBSD 10.2-RELEASE-p5 r289218

Deadlock is on an SSD-only mirrored ZFS pool:

home               ONLINE       0     0     0
  mirror-0         ONLINE       0     0     0
    gpt/mirror0-a  ONLINE       0     0     0
    gpt/mirror0-b  ONLINE       0     0     0
  mirror-1         ONLINE       0     0     0
    gpt/mirror1-a  ONLINE       0     0     0
    gpt/mirror1-b  ONLINE       0     0     0
  mirror-2         ONLINE       0     0     0
    gpt/mirror2-a  ONLINE       0     0     0
    gpt/mirror2-b  ONLINE       0     0     0
  mirror-3         ONLINE       0     0     0
    gpt/mirror3-a  ONLINE       0     0     0
    gpt/mirror3-b  ONLINE       0     0     0

The deadlocked process is a chksetuid run from periodic. The affected directory
is identified. Here is a procstat -kk output:

 1816 102485 find             -                mi_switch+0xe1
sleepq_wait+0x3a _sleep+0x287 vnode_create_vobject+0x100
zfs_freebsd_open+0xf5 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234
vn_open_cred+0x33e kern_openat+0x26f amd64_syscall+0x33a Xfast_syscall+0xfb

Trying to ls the affected directory ends up in the same:

71376 102400 ls               -                mi_switch+0xe1
sleepq_wait+0x3a _sleep+0x287 vnode_create_vobject+0x100
zfs_freebsd_open+0xf5 VOP_OPEN_APV+0xa1 vn_open_vnode+0x234
vn_open_cred+0x33e kern_openat+0x26f amd64_syscall+0x33a Xfast_syscall+0xfb

However, I'm able to list directory entries via zdb(8).

The processes are not killable.
The machine is running and non-productive, so I'm able to give any debugging
information, just give me some pointers.

Attached is the output from procstat -a -kk.

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