root fs switching to read only?

[Lonni J Friedman]

On Wed, Oct 15, 2008 at 6:01 AM, Dan Martin <dc.martin at verizon.net> wrote:
> Hi All,
>
> I'm testing  SLES10 SP2. We want to be able to rsync data from a running
> machine
> to the SLES10 SP2 test  machine.  rsync'ing to 2 different
> filesystems, we get  errors about the filesystem being readonly:
>
> rsync: failed to set times on "/usr/OSAS651/data": Read-only file system
> (30)
> sent 174782634 bytes  received 105572 bytes  2480683.77 bytes/sec
> total size is 3912215563  speedup is 22.37
> rsync error: some files could not be transferred (code 23) at main.c(892)
> [sende
> r=2.6.8]
>
> /usr/OSAS651 is the mount point.  data is a subdirectory.  We mount by
> Volume label.
>
> Coincidentally, the root  fs is also  broken at the moment, that is, it is
> set to read-only. We use LVM for all filesystems
> except  for root and boot.  All filesystems are ext3.  We have about 8
>  other ext3
> filesystems that are all writeable, even though root is not, and
> /usr/OSAS651 is not.  I  noticed the first failure while rsyncing to
> another filesystem,  /home.  Rebooting took care of that.  Then it broke
> again when I tried rsyncing to /usr/OSAS651, and I noticed that  root is
> now also read-only.  I don't know if root went read-only on the first
> rsync pass.  I doubt that rsync is causing the problem because we've used
> it without problems in similar scenarios.

First, fsck the filesystem.  If the problem returns, then you almost
certainly have faulty HW.



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                                    netllama at gmail.com
LlamaLand                       https://netllama.linux-sxs.org