[issue1695] NFS-related system breakdown
Stathis Kamperis (via DragonFly issue tracker)
sinknull at leaf.dragonflybsd.org
Sat Mar 13 14:23:10 PST 2010
New submission from Stathis Kamperis <ekamperi at gmail.com>:
I do a cp(1) from /mnt/nfs (which is a zfs fileystem NFS-exported by an
opensolaris installation) to my /home/beket directory (HAMMER fs).
After a few MBs having being copied, cp(1) process stalls in 'getblk' state.
Also it is unkillable by ^C. From that point there's downhill.
Many commands will block if I issue them, such as 'mount' or 'df'. I can still
view top(1) update its contents but the system is on the edge. dmesg shows
sparse messages 'nfs server 10.0.0.1:/export/nfs: not responding' or
'[diagnostic]: $address block on cache_something ""'. If I break into the
debugger, I get nothing unusual. scgetc < sckbdevent < kbd_xxxx < taskqueue_yyyy
I tried to kill X and the system hang to the point that a cold reset was
necessary. I once managed to resume after typing 'c' in db> prompt, but that
doesn't always succeed.
This situation is, I think, 100% reproducible. Also, I don't have problems
copying stuff from|to a linux NFS client.
keyword: HAMMER, kernel
title: NFS-related system breakdown
DragonFly issue tracker <bugs at lists.dragonflybsd.org>
More information about the Bugs