WARNING(virus check bypassed): Re: NFS - some success

[brad.mugleston at comcast.net]

On Mon, 5 Sep 2005, Mark Knecht wrote:

> On 9/5/05, brad.mugleston at comcast.net <brad.mugleston at comcast.net> wrote:
> >
> > /etc/fstab (client)
> > 192.168.1.55:/music /mnt/music nfs rw,hard,intr 0 0
> > c1911a1:/photos /mnt/photos nfs rw,hard,intr 0 0
> >
>
> Hi Brad,
>    Cool that you got it working.
>
>    One thing I've run into with NFS mounts is that rebooting with one
> mounted can cause problems and long delays. Rick Stevens pointed me
> toward an option called '_netdev' in man mount. (I think)  Using this
> option tells the system that networking must be up before this is
> mounted and that this must be unmounted before networking goes down.
> Good option. Here's a few NFS oriented entries from my machine's fstab
> file for you to peruse:
>
> dragonfly:/Musiclib     /mnt/Musiclib           nfs
> noauto,user,rw,_netdev,proto=udp        0 0
> dragonfly:/home/mark/MusicLib /home/mark/RemoteMusicLib/ nfs
> noauto,user,rw,_netdev  0 0
> myth14:/video           /video                  nfs
> auto,user,rw,_netdev,tcp,rsize=8192     0 0
>
> Note the inconsistencies! 'proto=udp' vs. 'tcp'. Who knows?! ;-) I
> should probably clean that up.
>
> Cheers,
> Mark
>

Mark,

Thanks for writing - So far I havent had that problem - I think
the "hard" command is suppose to keep me from having problems if
the server is down or something like that.

I'll do some reading and see what you have set up - maybe it will
help with my read/write problem.

Brad