Filesystem gone readonly
cax0cn at gmail.com
Sat Apr 25 14:09:21 UTC 2009
I agree with Christian, before running fsck, you should have a look on the
hardware status. If it's not a file system issue, running fsck may cause
terrible amount of files lost.
Additionally, you need to create a backup with the help of dd before any
fsck, so that you are able to recover some lost files.
Joe.c @ http://admon.org/
On Sat, Apr 25, 2009 at 12:04 PM, Eric Sandeen <sandeen at redhat.com> wrote:
> Hiren Joshi wrote:
> > I've got a really weird situation here. I'm using RHEL 4 and connecting
> > to an EMC storage device using fibre and qla2300.
> > 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:
> > fsck 1.35 (28-Feb-2004)
> > e2fsck 1.35 (28-Feb-2004)
> > Pass 1: Checking inodes, blocks, and sizes
> > Inode 2392655 has illegal block(s). Clear? no
> > Illegal block #9 (4101620032) in inode 2392655. IGNORED.
> > Inode 2392655, i_blocks is 672, should be 664. Fix? no
> Is there any chance that some other node on the san has this lun
> mounted, or is writing to it?
> Ext3-users mailing list
> Ext3-users at redhat.com
Sponser and operater: Linux monitoring solution: http://admon.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ext3-users