From: J G Miller on
On Thu, 05 Aug 2010 12:15:42 -0500, Ignoramus16841 wrote:

> standard nfs client

but using NFS v3 or v4?

> Yes. I am not sure yet what exactly is going on.

Could be some sort of timing bug in the NFS server code?

From: Ignoramus16841 on
On 2010-08-05, J G Miller <miller(a)yoyo.ORG> wrote:
> On Thu, 05 Aug 2010 12:15:42 -0500, Ignoramus16841 wrote:
>
>> standard nfs client
>
> but using NFS v3 or v4?

NFS 3

>> Yes. I am not sure yet what exactly is going on.
>
> Could be some sort of timing bug in the NFS server code?
>

It could be anything, but I am more inclined to blame the client, as

1) Many clients work just fine
2) Even my bad desktop works fine when it connects after a reboot
From: Rahul on
Ignoramus16841 <ignoramus16841(a)NOSPAM.16841.invalid> wrote in news:5
_KdnW29vrfPisbRnZ2dnUVZ_rmdnZ2d(a)giganews.com:

> Could be some sort of timing bug in the NFS server code?
>>
>
> It could be anything, but I am more inclined to blame the client, as
>
> 1) Many clients work just fine
> 2) Even my bad desktop works fine when it connects after a reboot
>

Does it matter if it is a soft or hard mount?

I'm just guessing here. I've a long mount option string on my server:

eustorage:/opt /opt nfs rw,nodev,noatime,nfsvers=3,timeo=110,retrans=
50,hard,intr,proto=udp,rsize=32768,wsize=32768 0 0

But I'd be hard pressed to explain why I chose each option that I have in
there. :)


--
Rahul
From: Grant on
On Thu, 05 Aug 2010 10:48:05 -0500, Ignoramus16841 <ignoramus16841(a)NOSPAM.16841.invalid> wrote:

>I have a desktop at work that has several NFS mounted filesystems that
>it picks from a few servers.
>
>When my computer boots, it mounts all of them and it is great. After a
>while (like a day), two mounts (both point to the same server) simply
>hang.
>
>*) If I do ls -l /x it hangs forever.
>*) If I do umount -l -f /x, it unmounts
>*) If I then do mount /x, it hangs forever. Strace says
>
>[pid 20657] close(3) = 0
>[pid 20657] time(NULL) = 1281021699
>[pid 20657] mount("server:/directory", "/x", "nfs", MS_RDONLY, "rsize=8192,wsize=8192,intr,addr="...^C <unfinished ...>
>
>*) At the same time, other filesystems (from other servers) work
>great.
>*) Restarting nfs-common or portmap does NOT help.
>
>I am totally stumped as to what could be going on. Any ideas?

I had a problem with slackware-13.1 where I needed to add vers=3 to
stop the default nfs4 client throwing an error, worth a try?

deltree:/home/common /home/common nfs hard,intr,vers=3
deltree:/home/mirror /home/mirror nfs noauto,user,hard,intr,vers=3

Grant.
From: Ignoramus16841 on
On 2010-08-05, Grant <omg(a)grrr.id.au> wrote:
> On Thu, 05 Aug 2010 10:48:05 -0500, Ignoramus16841 <ignoramus16841(a)NOSPAM.16841.invalid> wrote:
>
>>I have a desktop at work that has several NFS mounted filesystems that
>>it picks from a few servers.
>>
>>When my computer boots, it mounts all of them and it is great. After a
>>while (like a day), two mounts (both point to the same server) simply
>>hang.
>>
>>*) If I do ls -l /x it hangs forever.
>>*) If I do umount -l -f /x, it unmounts
>>*) If I then do mount /x, it hangs forever. Strace says
>>
>>[pid 20657] close(3) = 0
>>[pid 20657] time(NULL) = 1281021699
>>[pid 20657] mount("server:/directory", "/x", "nfs", MS_RDONLY, "rsize=8192,wsize=8192,intr,addr="...^C <unfinished ...>
>>
>>*) At the same time, other filesystems (from other servers) work
>>great.
>>*) Restarting nfs-common or portmap does NOT help.
>>
>>I am totally stumped as to what could be going on. Any ideas?
>
> I had a problem with slackware-13.1 where I needed to add vers=3 to
> stop the default nfs4 client throwing an error, worth a try?
>
> deltree:/home/common /home/common nfs hard,intr,vers=3
> deltree:/home/mirror /home/mirror nfs noauto,user,hard,intr,vers=3
>
> Grant.

Does not help, unfortunately.

i