Getting Started, Documentation, Tips & Tricks

nfs timeout

While I'm in the guts fixing stuff, does anyone know offhand where to adjust the timeout settings for nfs ? Whenever a mounted nfs share goes offline, my desktop goes dead forever waiting for it to respond. Not exactly dead but all the graphical elements quit working such as the file windows, pasting text to the desktop, drag and drop and so on.

And I do mean forever . Long enough to go make a peanut butter and jelly sandwich, eat it, take a pee and wash your hands, come back but Irix is still looking for the missing directory. It's tragic :(

_________________
waiting for flight 1203 ...
morning ham! we got 3 days holiday ;)

hmm not sure this helps: fstab

then

timeo=n Set NFS timeout to n tenths of a second. (Default = 11)

_________________
:Octane: (Sakura) :O2: (Sasuke) :1600SW: (Naruto) ... lil Jesse! (O2 laptop)
“Imagination is more important than knowledge.“ – A. Einstein
geo wrote:
morning ham! we got 3 days holiday ;)

Right ! Except then you have to work on Sunday to make up for the third day :D

We have an unusual concept of a three day holiday ...

fstab wrote:
timeo=n Set NFS timeout to n tenths of a second. (Default = 11)

Good idear, thanks. I'll give this a shot and report back.

_________________
waiting for flight 1203 ...
While you're at it, have a look at the fstab(4) man page, and try combinations of 'hard' vs. 'soft' and 'intr' vs. 'nointr'.

The default is apparenly 'hard' which will make the system retry until the server responds. Maybe you'd prefer 'soft'?

You can probably interrupt it with a suitable signal thanks to the 'intr' option being on by default...unless that's been changed on your system.

_________________
:Indigo2IMP: :Octane: :Indigo: :O3x0:
Sun SPARCstation 20, Blade 2500
HP C8000
jpstewart wrote:
Maybe you'd prefer 'soft'?

Thanks very much but so far, no :P

_________________
waiting for flight 1203 ...
jpstewart wrote:
The default is apparenly 'hard' which will make the system retry until the server responds. Maybe you'd prefer 'soft'?


Thanks, that may be useful for me. I don't power on all my boxes very often. Due to changes in the network shares and so on, I normally have a lot of "NFS timeout" messages and have to boot in single mode to vi-edit fstab... Very annoying.

Do you know by chance if there is a way to specify the number of connections trials before ignoring a network mount during OS startup ?

_________________
:Onyx2: 4xR12k 400, 8Gb, IR2E, 2x18+3x73GB HD (oxygen)
:A3504L: :A3504L: 16xItanium2 1.6, L2 9MB (neon)
:Fuel: R16k 800 V12, 2Gb, M-Audio, 36+147GB HD, 3Dconnexion SpaceMouse Classic (nitrogen)
:Octane2: Dual R14k 600 V6, 2Go, HD (173Go, 34Go) (carbon)
:Octane: R10k 400 MXE, 1280Mo (lithium) / 2xR10k 300 SSE,... (fluorine)
:O2: R10k 195, 512Mo (hydrogen) / R5k 180, 512Mo (sodium) / R5k 180->200 motherboard and PM only
:Indigo2IMP: R10k 195, HighImpact, 160Mo (helium) / R4400 125, Extreme, 160Mo (boron)
:O200: :O200: twin O200, 4xR12k 270, 2Go, HD (4x18Go) (beryllium)
:Indigo: R4k 100, 80Mo, LG1, 9GB HD, Python 25601 tape (magnesium])
:4D70G: 4D70GT... my very first one (now property of musée bolo and the foundation mémoires informatiques )
See the hinv/gfxinfo posts here .
Sorry, I asked before even trying to find it out by myself.
Now I did it and it seems it should be pretty easy... One or more of the following arguments will probably do the job just fine:
Code:
bg        If the first attempt fails, retry in the background.
retry=n   Set number of mount failure retries to n. (Default = 10000)
timeo=n   Set NFS timeout to n tenths of a second. (Default = 11)
soft      Return error if server doesn't respond.

Regarding the "soft" option, be carefull that
Code:
Filesystems that are mounted rw (read-write) should use the hard option.

So, "retry=n" may be a better solution, or even "bg", if it doesn't slow the system too much... (how to abort if needed ?).

_________________
:Onyx2: 4xR12k 400, 8Gb, IR2E, 2x18+3x73GB HD (oxygen)
:A3504L: :A3504L: 16xItanium2 1.6, L2 9MB (neon)
:Fuel: R16k 800 V12, 2Gb, M-Audio, 36+147GB HD, 3Dconnexion SpaceMouse Classic (nitrogen)
:Octane2: Dual R14k 600 V6, 2Go, HD (173Go, 34Go) (carbon)
:Octane: R10k 400 MXE, 1280Mo (lithium) / 2xR10k 300 SSE,... (fluorine)
:O2: R10k 195, 512Mo (hydrogen) / R5k 180, 512Mo (sodium) / R5k 180->200 motherboard and PM only
:Indigo2IMP: R10k 195, HighImpact, 160Mo (helium) / R4400 125, Extreme, 160Mo (boron)
:O200: :O200: twin O200, 4xR12k 270, 2Go, HD (4x18Go) (beryllium)
:Indigo: R4k 100, 80Mo, LG1, 9GB HD, Python 25601 tape (magnesium])
:4D70G: 4D70GT... my very first one (now property of musée bolo and the foundation mémoires informatiques )
See the hinv/gfxinfo posts here .
option "bg" is the common cure for that. especially in larger lans that's pretty much a must.

_________________
r-a-c.de
Thanks for the info. I'll do that.

_________________
:Onyx2: 4xR12k 400, 8Gb, IR2E, 2x18+3x73GB HD (oxygen)
:A3504L: :A3504L: 16xItanium2 1.6, L2 9MB (neon)
:Fuel: R16k 800 V12, 2Gb, M-Audio, 36+147GB HD, 3Dconnexion SpaceMouse Classic (nitrogen)
:Octane2: Dual R14k 600 V6, 2Go, HD (173Go, 34Go) (carbon)
:Octane: R10k 400 MXE, 1280Mo (lithium) / 2xR10k 300 SSE,... (fluorine)
:O2: R10k 195, 512Mo (hydrogen) / R5k 180, 512Mo (sodium) / R5k 180->200 motherboard and PM only
:Indigo2IMP: R10k 195, HighImpact, 160Mo (helium) / R4400 125, Extreme, 160Mo (boron)
:O200: :O200: twin O200, 4xR12k 270, 2Go, HD (4x18Go) (beryllium)
:Indigo: R4k 100, 80Mo, LG1, 9GB HD, Python 25601 tape (magnesium])
:4D70G: 4D70GT... my very first one (now property of musée bolo and the foundation mémoires informatiques )
See the hinv/gfxinfo posts here .