On Wed, 14 Nov 2007, Christian Kujau wrote:
Yes, the nfsd process only got stuck when I did ls(1) (with or without -l) on
a NFS share which contained a XFS partition.
Since NFS was not working (the nfsd processes were already in D state), to
mount a CIFS share from the very same server (and the same client). I'm
exporting the same /data share (JFS), but, since it's smbd I don't have to
export every single submount (as it is with NFS):
* with NFS:
* with CIFS:
server:/data (containing both the jfs and the xfs partition as one
single share to mount)
Upon accessing the /data/sub part of the CIFS share, the client hung,
waiting for the server to respond (the [cifs] kernel thread on the client
was spinning, waiting for i/o). On the server, similar things as with the
nfsd processes happened (although I know that the smbd (Samba) processes
are running completely in userspace):
Sysrq-t again on the server:
smbd D c04131c0 0 22782 3039
e242ad60 00000046 e242a000 c04131c0 00000001 e7875264 00000246 e7f88a80
e242ada8 c040914c 00000000 00000002 c016dc64 e7a3b7b8 e242a000 e7875284
00000000 c016dc64 f7343d88 f6337e90 e7f88a80 e7875264 e242ad88 e7a3b7b8
So, it's really not NFS but ?FS related?
BOFH excuse #199:
the curls in your keyboard cord are losing electricity.