Filesystem gone readonly

Christian Kujau lists at
Sat Apr 25 03:38:34 UTC 2009

On Sat, 11 Apr 2009, Hiren Joshi wrote:
> The luns are put into LVM and we have a number of 400G partitions coming off
> that, I made a snapshot and ran fsck -yn on it with the following output:

Why did you run fsck? Did you suspect filesystem errors, i.e. were there 
other reasons to run fsck in the first place? (unclean shutdown, power 
outages, etc.)

> fsck 1.35 (28-Feb-2004)
> e2fsck 1.35 (28-Feb-2004)

e2fsprogs-1.41.5 has been released[0] today, you may want to upgrade these 
before doing anything to the filesystem.

Also, was there anything devices related in the kernel logs? Can you read 
off the raw LVM device w/o errors? When did the errors start / when 
was your last fsck with no errors reported? It's strange that the 
filesystem starts to show errors "out of the blue", so I'm fishing for 
hardware related issues, because: if it's software related, you'd have to 
upgrade the ext3 "driver", i.e. the kernel - probably not possible for 
w/o breaking ot of RHEL4.


Bruce Schneier isn't fooled by decoy states.

More information about the Ext3-users mailing list