Not sure where to ask this question so I'll try here. I have a Raid 0
EXT3 file system that is coming up read only. I don't think it's raid
related but not sure why it's stuck on read only.
When I run mount it shows:
/dev/md0 on /data type ext3 (rw,noatime)
But when I attempt (running as root) to change anything I get:
touch: cannot touch `x': Read-only file system
When I list the directory I get this:
drwxr-xr-x 8 root root 4096 Sep 29 15:15 .
drwxr-xr-x 45 root root 4096 Oct 4 10:42 ..
drwxr-xr-x 4 root root 4096 Sep 11 03:17 critical
drwx------ 2 root root 16384 Sep 10 22:37 lost+found
drwxr-xr-x 19 root root 4096 Sep 11 02:07 mirror
dr-x------ 14 root root 4096 Sep 9 09:52 Robin
drwxr-xr-x 7 root root 4096 Oct 5 02:16 snapshot
drwxrwxr-x+ 289 root root 12288 Oct 1 03:20 www
Note the weird permissions on Robin. This happened because I was trying
to save data from a crashed Windows NT system and I used rsync to copy
the data over. And I noticed the problem around the same time.
So - what can I do to fix this?
On Fri, Oct 06, 2006 at 09:28:02AM -0700, Marc Perkel wrote:
> Not sure where to ask this question so I'll try here. I have a Raid 0 EXT3 file system that is coming up read
> only. I don't think it's raid related but not sure why it's stuck on read only.
>
> When I run mount it shows:
> /dev/md0 on /data type ext3 (rw,noatime)
>
> But when I attempt (running as root) to change anything I get:
> touch: cannot touch `x': Read-only file system
>
> When I list the directory I get this:
> drwxr-xr-x 8 root root 4096 Sep 29 15:15 .
> drwxr-xr-x 45 root root 4096 Oct 4 10:42 ..
> drwxr-xr-x 4 root root 4096 Sep 11 03:17 critical
> drwx------ 2 root root 16384 Sep 10 22:37 lost+found
> drwxr-xr-x 19 root root 4096 Sep 11 02:07 mirror
> dr-x------ 14 root root 4096 Sep 9 09:52 Robin
> drwxr-xr-x 7 root root 4096 Oct 5 02:16 snapshot
> drwxrwxr-x+ 289 root root 12288 Oct 1 03:20 www
>
> Note the weird permissions on Robin. This happened because I was trying to save data from a crashed Windows
> NT system and I used rsync to copy the data over. And I noticed the problem around the same time.
>
> So - what can I do to fix this?
Does your dmesg have some info on this?
Regards,
Frederik
On Fri, 06 Oct 2006, Marc Perkel wrote:
> Not sure where to ask this question so I'll try here. I have a Raid 0
> EXT3 file system that is coming up read only. I don't think it's raid
> related but not sure why it's stuck on read only.
1. check dmesg
2. run a recent version of e2fsprogs (aka e2fsck)
--
Matthias Andree