Probblem with NFS mount

[Michael Song]

Hi, Rob
Below is the 'cat /proc/mounts' output:
# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / nfs
rw,v2,rsize=4096,wsize=4096,hard,nolock,proto=udp,addr=192.168.0
proc /proc proc rw,nodiratime 0 0

It shows 'rw',


Thanks


----- Original Message -----
From: "Rob Landley" <rob at landley.net>
To: <busybox at busybox.net>
Cc: "Michael Song" <song_michael at hotmail.com>; <busybox at mail.busybox.net>
Sent: Tuesday, May 02, 2006 1:34 PM
Subject: Re: Probblem with NFS mount


> On Tuesday 02 May 2006 12:49 am, Michael Song wrote:
> > Hello, BusyBox folks
> > I have the following NFS  rootfs mount problem.
> > I have verified that the server is OK, and it give write access to
> > client(verified seperately with a different Linux work station) the
mount
> > status shows I have read and write access,
> > but when I try to write to it, I got Read-only file system error
>
> That error comes from the kernel, so the kernel thinks it's read-only.
>
> > BusyBox v1.1.2 (2006.04.29-09:07+0000) Built-in shell (ash)
> > Enter 'help' for a list of built-in commands.
>
> This worked for some people...
>
> > # mount
> > /dev/root on / type nfs
> > (rw,v2,rsize=4096,wsize=4096,hard,nolock,proto=udp,addr) proc on /proc
type
> > proc (rw,nodiratime)
> > # touch xxx
> > touch: xxx: Read-only file system
>
> Do you have legacy mtab support enabled?  If so cat /proc/mounts to see
what
> the kernel _really_ thinks...
>
> Also check dmesg to see if the sucker got remounted read only, although it
> shouldn't be...
>
> Rob
> --
> Never bet against the cheap plastic solution.
>