* NFS problem (r/o filesystem) with 2.6.19-rc3
@ 2006-10-28 18:42 Ken Moffat
2006-10-28 21:22 ` Andrew Morton
0 siblings, 1 reply; 3+ messages in thread
From: Ken Moffat @ 2006-10-28 18:42 UTC (permalink / raw)
To: linux-kernel
Hi,
yesterday I moved this desktop box to -rc3 from 2.6.18. I have a
large amount of data on nfs mounts (r/w) and everything looks good.
But, for my backups I have cron jobs to mount a different nfs
filesystem and rsync to it. That fails with 2.6.19-rc3, giving me
messages like
about to mount /nfs
Sat Oct 28 18:45:03 BST 2006 rsyncing
rsync: failed to set times on "/nfs/bluesbreaker/boot/.": Read-only
file system (30)
rsync: mkstemp "/nfs/bluesbreaker/boot/.map.c2Cj91" failed:
Read-only file system (30)
rsync: mkstemp
"/nfs/bluesbreaker/boot/.vmlinuz-2.6.19-rc3-sda8.pXKgH9" failed:
Read-only file system (30)
rsync: failed to set times on "/nfs/bluesbreaker/boot/.": Read-only
file system (30)
rsync error: some files could not be transferred (code 23) at
main.c(791)
rsync failed
umounting /nfs
If I mount it manually, it seems to be ok -
root@bluesbreaker /home/ken #mount
/dev/sda8 on / type auto (rw)
[...]
deepthought:/data/staging on /nfs type nfs (rw,hard,intr,tcp,addr=192.168.0.10)
root@bluesbreaker /home/ken #
But if I then try to touch a file I find the filesystem is r/o -
root@bluesbreaker /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 ?
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: NFS problem (r/o filesystem) with 2.6.19-rc3
2006-10-28 18:42 NFS problem (r/o filesystem) with 2.6.19-rc3 Ken Moffat
@ 2006-10-28 21:22 ` Andrew Morton
2006-10-28 22:58 ` Ken Moffat
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Morton @ 2006-10-28 21:22 UTC (permalink / raw)
To: Ken Moffat; +Cc: linux-kernel, Trond Myklebust
On Sat, 28 Oct 2006 19:42:27 +0100
Ken Moffat <zarniwhoop@ntlworld.com> wrote:
> Hi,
>
> yesterday I moved this desktop box to -rc3 from 2.6.18. I have a
> large amount of data on nfs mounts (r/w) and everything looks good.
> But, for my backups I have cron jobs to mount a different nfs
> filesystem and rsync to it. That fails with 2.6.19-rc3, giving me
> messages like
>
> about to mount /nfs
> Sat Oct 28 18:45:03 BST 2006 rsyncing
> rsync: failed to set times on "/nfs/bluesbreaker/boot/.": Read-only
> file system (30)
> rsync: mkstemp "/nfs/bluesbreaker/boot/.map.c2Cj91" failed:
> Read-only file system (30)
> rsync: mkstemp
> "/nfs/bluesbreaker/boot/.vmlinuz-2.6.19-rc3-sda8.pXKgH9" failed:
> Read-only file system (30)
> rsync: failed to set times on "/nfs/bluesbreaker/boot/.": Read-only
> file system (30)
> rsync error: some files could not be transferred (code 23) at
> main.c(791)
> rsync failed
> umounting /nfs
>
> If I mount it manually, it seems to be ok -
> root@bluesbreaker /home/ken #mount
> /dev/sda8 on / type auto (rw)
> [...]
> deepthought:/data/staging on /nfs type nfs (rw,hard,intr,tcp,addr=192.168.0.10)
> root@bluesbreaker /home/ken #
>
> But if I then try to touch a file I find the filesystem is r/o -
> root@bluesbreaker /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 ?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: NFS problem (r/o filesystem) with 2.6.19-rc3
2006-10-28 21:22 ` Andrew Morton
@ 2006-10-28 22:58 ` Ken Moffat
0 siblings, 0 replies; 3+ messages in thread
From: Ken Moffat @ 2006-10-28 22:58 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, Trond Myklebust
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@ntlworld.com> wrote:
>
> > But if I then try to touch a file I find the filesystem is r/o -
> > root@bluesbreaker /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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-10-28 22:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-28 18:42 NFS problem (r/o filesystem) with 2.6.19-rc3 Ken Moffat
2006-10-28 21:22 ` Andrew Morton
2006-10-28 22:58 ` Ken Moffat
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox