[wplug] Writing to a NFS mount

[Keir Josephson]

I'm guessing that you've set up a permanent NFS mount? Your might want to
try seting up the automounter instead. Have you tried to reset the client
configuration?

-Keir

On Fri, 12 Sep 2003, Alexandros Papadopoulos wrote:

> On Thursday 11 September 2003 23:20, Gentgeen wrote:
> > A little while ago, I set up a NFS share on my laptop.  I used my
> > desktop machine to edit some of the file, then forgot to unmount when
> > I was done.  I then had to do a forced unmount the next day when I
> > realized my mistake.
> >
> > The problem is now I can mount the laptop drive, but I can not write
> > to it anymore.  I can mount, browse, and read the laptop drive, just
> > not write to it.  I can't remember all the things I had to do to set
> > it up, so I am having some trouble with troubleshooting the problem. 
> > I also can't find the webpage that I used to help set it up (I
> > thought I bookmarked it, but guess not)
> >
> > My desktop box is a Redhat 7.2 system at 192.168.0.2.
> > The fstab line is:
> >    192.168.0.4:/home/kevin /mnt/littlebox		nfs
> > rsize=8192,wsize=8192,timeo=14,intr,noauto,user 0 0
> <snip>
> > ------------------------------------------
> > My laptop is a Debian Woody 3.0 system at 192.168.0.4
> > The hosts.allow file has:
> >    portmap:	192.168.0.3
> >    lockd:	192.168.0.3
> >    rquotad:	192.168.0.3
> >    mountd:	192.168.0.3
> >    statd:	192.168.0.3
> >
> > The hosts.deny file has:
> >    portmap:ALL
> >    lockd:ALL
> >    rquotad:ALL
> >    mountd:ALL
> >    statd:ALL
> >
> > The exports file has:
> >    /home/kevin 192.168.0.3(rw)
> 
> Well, your client is at 192.168.0.2, but you're exporting the filesystem 
> from Debian to 192.168.0.3. I guess that's just a typo in your email, 
> since in that case you shouldn't be able to mount it at all.
> 
> Try forcing the server to re-read its exports with
> # exportfs -r -v 
> 
> Also, you might want to add the option rw to your client fstab entry.
> 
> If that doesn't help it, monitor your logs with 
> # tail -f /var/log/messages 
> on the server, the moment you try to mount your NFS share - that should 
> give you more clues about what's happening.
> 
> -A
> -- 
> http://andrew.cmu.edu/~apapadop/pub_key.asc
> 3DAD 8435 DB52 F17B 640F  D78C 8260 0CC1 0B75 8265
>