[Bug 204764] Filesystem deadlock, process in vodead state

[bugzilla-noreply at freebsd.org]

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

--- Comment #4 from Daniel Ylitalo <daniel at blodan.se> ---
Okay! Got a proc stuck again, however, I'm having trouble understanding "find
the vnode address which caused the hang", how do I know what caused the hang?

Heres all the output I've gatherd so far:


procstat -kk -a
=====================================
94614 100627 python2.7        -                mi_switch+0x179
sleepq_switch+0x152 sleepq_wait+0x43 _sleep+0x366 vnode_create_vobject+0xe9
ufs_lookup_ino+0xa0 VOP_CACHEDLOOKUP_APV+0x10f vfs_cache_lookup+0xd6
VOP_LOOKUP_APV+0x10f lookup+0x5c2 namei+0x504 kern_statat_vnhook+0xae
sys_lstat+0x30 amd64_syscall+0x278 Xfast_syscall+0xfb
=====================================
[root at hub-se /usr/obj/usr/src/sys/GENERIC]# kgdb kernel.debug /dev/mem
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
Reading symbols from /boot/kernel/aio.ko.symbols...done.
Loaded symbols for /boot/kernel/aio.ko.symbols
Reading symbols from /boot/kernel/accf_data.ko.symbols...done.
Loaded symbols for /boot/kernel/accf_data.ko.symbols
Reading symbols from /boot/kernel/accf_http.ko.symbols...done.
Loaded symbols for /boot/kernel/accf_http.ko.symbols
Reading symbols from /boot/kernel/fdescfs.ko.symbols...done.
Loaded symbols for /boot/kernel/fdescfs.ko.symbols
Reading symbols from /boot/kernel/nullfs.ko.symbols...done.
Loaded symbols for /boot/kernel/nullfs.ko.symbols
#0  sched_switch (td=0xffffffff81850720, newtd=<value optimized out>,
flags=<value optimized out>) at /usr/src/sys/kern/sched_ule.c:1945
1945                    cpuid = PCPU_GET(cpuid);

(kgbd) info threads
  505 Thread 100627 (PID=94614: python2.7)  sched_switch
(td=0xfffff80379b5e940, newtd=<value optimized out>, flags=<value optimized
out>) at /usr/src/sys/kern/sched_ule.c:1945

(kgdb) thread 505
[Switching to thread 505 (Thread 100627)]#0  sched_switch
(td=0xfffff80379b5e940, newtd=<value optimized out>, flags=<value optimized
out>) at /usr/src/sys/kern/sched_ule.c:1945
1945                    cpuid = PCPU_GET(cpuid);
(kgdb) bt
#0  sched_switch (td=0xfffff80379b5e940, newtd=<value optimized out>,
flags=<value optimized out>) at /usr/src/sys/kern/sched_ule.c:1945
#1  0xffffffff8094e149 in mi_switch (flags=260, newtd=0x0) at
/usr/src/sys/kern/kern_synch.c:491
#2  0xffffffff8098bb02 in sleepq_switch (wchan=<value optimized out>,
pri=<value optimized out>) at /usr/src/sys/kern/subr_sleepqueue.c:538
#3  0xffffffff8098b963 in sleepq_wait (wchan=0xfffff808cdd41e00, pri=84) at
/usr/src/sys/kern/subr_sleepqueue.c:617
#4  0xffffffff8094da56 in _sleep (ident=<value optimized out>, lock=<value
optimized out>, priority=<value optimized out>, wmesg=<value optimized out>,
sbt=<value optimized out>, pr=<value optimized out>)
    at /usr/src/sys/kern/kern_synch.c:255
#5  0xffffffff80be8759 in vnode_create_vobject (vp=0xfffff8036ee569c0,
isize=512, td=0xfffff80379b5e940) at /usr/src/sys/vm/vnode_pager.c:120
#6  0xffffffff80bb1010 in ufs_lookup_ino (vdp=0xfffff8036ee569c0,
vpp=0xfffffe0a5bdfd9a8, cnp=0xfffffe0a5bdfd9d0, dd_ino=0x0) at
/usr/src/sys/ufs/ufs/ufs_lookup.c:259
#7  0xffffffff80e791ef in VOP_CACHEDLOOKUP_APV (vop=<value optimized out>,
a=<value optimized out>) at vnode_if.c:197
#8  0xffffffff809dba26 in vfs_cache_lookup (ap=<value optimized out>) at
vnode_if.h:80
#9  0xffffffff80e7902f in VOP_LOOKUP_APV (vop=<value optimized out>, a=<value
optimized out>) at vnode_if.c:129
#10 0xffffffff809e40c2 in lookup (ndp=0xfffffe0a5bdfd948) at vnode_if.h:54
#11 0xffffffff809e3764 in namei (ndp=0xfffffe0a5bdfd948) at
/usr/src/sys/kern/vfs_lookup.c:302
#12 0xffffffff809f911e in kern_statat_vnhook (td=0xfffff80379b5e940,
flag=<value optimized out>, fd=-100, path=0x8067103d4 <Error reading address
0x8067103d4: Bad address>, pathseg=UIO_USERSPACE, sbp=0xfffffe0a5bdfda60,
hook=0)
    at /usr/src/sys/kern/vfs_syscalls.c:2298
#13 0xffffffff809f92b0 in sys_lstat (td=0x0, uap=0xfffffe0a5bdfdb80) at
/usr/src/sys/kern/vfs_syscalls.c:2278
#14 0xffffffff80d51b38 in amd64_syscall (td=0xfffff80379b5e940, traced=0) at
subr_syscall.c:134
#15 0xffffffff80d359ab in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:396
#16 0x000000080157f8aa in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)


I'm letting the server stay stuck until I know how to get the info you need out
of it :)

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