bunzip2 in an uninterruptable sleep

Mark Hobley wrote:
> Dances With Crows <danceswithcrows@usa.net> wrote:
>
>> If machine N has an NFS filesystem mounted, and the NFS server providing
>> that filesystem barfs, all the processes on N that were using that
>> filesystem will get stuck in state D the next time they try to access
>> that filesystem.
>> (Unless machine N mounted the filesystem with "soft", of course.)
>
> Hmmm, the servers are running Debian stable, and have been providing NFS
> services for several years now, and have been working fine with Debian
> stable clients.
>
> The Gentoo machine is a new development on the network, with the NFS
> client becoming operational at the beginning of this year.
>
> Following a kernel upgrade last week, NFS now has a problem.
>
> I can navigate round the mounted filesystem, changing directories, etc,
> but if I try to cat a file, sometimes I get no output, and other
> times the process gets stuck in state D.
>
> I try to unmount the NFS filesystem, I get an error:
>
> umount: /volumes/vol3a: device is busy
>
> I stop and restart the nfs services on the server side, but client
> processes remain in state D on the Gentoo machine.
>
> I examine the NFS server side dmesg:
>
> nfsd: last server has exited
> nfsd: unexporting all filesystems
> RPC: failed to contact portmap (errno -5).
> NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
> NFSD: starting 90-second grace period
>
> I don't know what that RPC: failed to contact portmap (errno -5),
> portmap is running, and my other NFS clients are working fine.
>
> On the Gentoo client side, dmesg reveals:
>
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> nfs: server neptune not responding, still trying
> nfs: server neptune not responding, still trying
> nfs: server neptune OK
> nfs: server neptune OK
>
> ps reveals that portmap is running on the client side.
>
> I am running the nfs-kernel-server on the server side.
>
> I suspect that the new kernel version has introduced some
> incompatibility with existing NFS servers, but I don't know how to
> go about troubleshooting or diagnosing this.
>
> Mark.
>


MM.have a look here..

http://wiki.linux-nfs.org/wiki/index...o_Optimization


There area LOT of tuneables.

The Natural Philosopher <a@b.c> wrote:

> http://wiki.linux-nfs.org/wiki/index...o_Optimization

I reported the problem through http://bugzilla.linux-nfs.org (bug #163)

/proc/mounts on a working client reveals:

neptune:/volumes/vol3a/ /volumes/vol3a nfs rw,vers=3,rsize=32768,wsize=32768,
hard,intr,proto=tcp,timeo=600,retrans=2,sec=sys,ad dr=neptune 0 0

/proc/mounts on the hanging Gentoo client reveals:

neptune:/volumes/vol3a/ /volumes/vol3a nfs
rw,vers=3,rsize=32768,wsize=32768,hard,nointr,prot o=udp,timeo=7,retrans=3,sec=sys,addr=10.0.0.8
0 0

I have switched the client to tcp by using the using the '-o proto=tcp'
mount option, and it initially appears to be working ok.

Cheers,

Mark.

--
Mark Hobley,
393 Quinton Road West,
Quinton, BIRMINGHAM.
B32 1QE.