 NFS mount takes 5 minutes |
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom  |
 Jun 29 2004, 07:11 AM
Post
#1
|
|
 Group: Members Posts: 20 Joined: 15-December 03 From: Helvetia Member No.: 1,191  |
when i mount an nfs share like this:
CODE $ mount /mnt/foo it returns successfully after exactly 5 minutes consistently. I suspect this corresponds to a timeout or two /etc/fstab defines: CODE foo:/home /mnt/foo nfs defaults,nosuid,noauto i believe the problem is client related because two nfs servers (linux, bsd) both take 5 minutes to mount on the z but cross-mount instantly. server logs indicate only client de/authentication, nothing unexpected. is there client logging that i am unaware of? other ideas? thanks. |
 |
 
|
|
Jun 29 2004, 07:21 AM
Post
#2
|
|
 Group: Members Posts: 1,497 Joined: 12-November 03 From: Germany Member No.: 907 |
supply -nolock or install portmapper.
|
|
|
|
|
Jun 30 2004, 02:27 AM
Post
#3
|
|
|
Group: Members Posts: 20 Joined: 15-December 03 From: Helvetia Member No.: 1,191 |
thanks Mickey.
adding "nolock" to the mount options in fstab does the trick. |
|
|
|
|
Jun 30 2004, 06:46 AM
Post
#4
|
|
|
Group: Members Posts: 992 Joined: 9-October 03 From: NYC Member No.: 609 |
is that all it is! damn... I've been living with this forever...
but even after a mount -- an ls takes forever. check: http://zaurus.spy.org/screenshots/scottyelich/pdaXrom/jpg/ the "df" images... I normally would mount -o soft -t nfs blah & and then wait... wait... and wait... :-/ so, now... -o soft,nolock .. thanks! Scott |
|
|
|
|
Jun 30 2004, 08:57 AM
Post
#5
|
|
|
Group: Members Posts: 10 Joined: 19-March 04 Member No.: 2,399 |
I'm mounting from a NetBSD host and had to add nfsvers=2 to my mounts in order to
get throuput to more than about 50 KB/sec: server:/zaurus /mnt nfs noauto,hard,intr,nolock,async,nfsvers=2 0 0 Himchen |
|
|
|
|
Jul 5 2004, 04:06 PM
Post
#6
|
|
|
Group: Members Posts: 172 Joined: 13-April 04 Member No.: 2,827 |
QUOTE(ScottYelich @ Jun 30 2004, 06:46 AM) the "df" images... I normally would mount -o soft -t nfs blah & and then wait... wait... and wait... :-/ so, now... -o soft,nolock .. thanks! Scott -o soft ? It's far better to use -o hard,intr. From the man page for the mount command: hard The program accessing a file on a NFS mounted file system will hang when the server crashes. The pro╜ cess cannot be interrupted or killed unless you also specify intr. When the NFS server is back online the program will continue undisturbed from where it was. This is probably what you want. soft This option allows the kernel to time out if the nfs server is not responding for some time. The time can be specified with timeo=time. This option might be useful if your nfs server sometimes doesn't respond or will be rebooted while some pro╜ cess tries to get a file from the server. Usually it just causes lots of trouble. |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 22nd May 2013 - 09:28 PM |