I did just this and it looks like the memory is shot so
on one of the nodes so I'm doing all the work on the other node..... thanks for
the pointers!
Josh.
Hi, Hiren,
From: ext3-users-bounces@xxxxxxxxxx [mailto:ext3-users-bounces@xxxxxxxxxx] On Behalf Of Joseph Chen
Sent: 25 April 2009 15:09
To: Eric Sandeen
Cc: ext3-users@xxxxxxxxxx
Subject: Re: Filesystem gone readonly
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.
Good luck,
Joe.c @ http://admon.org/
On Sat, Apr 25, 2009 at 12:04 PM, Eric Sandeen <sandeen@xxxxxxxxxx> wrote:
Hiren Joshi wrote:Is there any chance that some other node on the san has this lun
> 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
mounted, or is writing to it?
-Eric
_______________________________________________
Ext3-users mailing list
Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users
--
Sponser and operater: Linux monitoring solution: http://admon.org
_______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
