linux-kernel - Re: NFS problem (r/o filesystem) with 2.6.19-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 28 Oct 2006 23:58:45 +0100
From:	Ken Moffat <zarniwhoop@...world.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org,
	Trond Myklebust <trond.myklebust@....uio.no>
Subject: Re: NFS problem (r/o filesystem) with 2.6.19-rc3

On Sat, Oct 28, 2006 at 02:22:28PM -0700, Andrew Morton wrote:
> On Sat, 28 Oct 2006 19:42:27 +0100
> Ken Moffat <zarniwhoop@...world.com> wrote:
> 
> >  But if I then try to touch a file I find the filesystem is r/o -
> > root@...esbreaker /home/ken #touch /nfs/bluesbreaker/boot/vmlinuz-2.6.18-sda8 
> > touch: cannot touch `/nfs/bluesbreaker/boot/vmlinuz-2.6.18-sda8':
> > Read-only file system
> > 
> >  This filesystem is a 'staging' area where whichever of my desktop
> > machines are up can write.  From a different box using a 2.6.17.13
> > kernel the filesystem is r/w.  The system log on the machine running
> > rc3 only shows that rsync ended in error, there are no associated
> > kernel messages. 
> > 
> >  Suggestions, please ?
> > 
> 
> Is it this: http://lkml.org/lkml/2006/10/18/264 ?

Yes, I think it is. 

Ken 
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/