<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16825" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=887004109-27042009>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!</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=887004109-27042009></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=887004109-27042009>Josh.</SPAN></FONT></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> ext3-users-bounces@redhat.com
[mailto:ext3-users-bounces@redhat.com] <B>On Behalf Of </B>Joseph
Chen<BR><B>Sent:</B> 25 April 2009 15:09<BR><B>To:</B> Eric
Sandeen<BR><B>Cc:</B> ext3-users@redhat.com<BR><B>Subject:</B> Re: Filesystem
gone readonly<BR></FONT><BR></DIV>
<DIV></DIV>Hi, Hiren,<BR><BR>I agree with <SPAN class=gI><SPAN class=gD
style="COLOR: rgb(121,6,25)">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.<BR>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.<BR><BR>Good luck,<BR>Joe.c @ <A
href="http://admon.org/">http://admon.org/</A><BR></SPAN></SPAN><BR>
<DIV class=gmail_quote>On Sat, Apr 25, 2009 at 12:04 PM, Eric Sandeen <SPAN
dir=ltr><<A
href="mailto:sandeen@redhat.com">sandeen@redhat.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV class=im>Hiren Joshi wrote:<BR>> I've got a really weird situation
here. I'm using RHEL 4 and connecting<BR>> to an EMC storage device using
fibre and qla2300.<BR>><BR>> The luns are put into LVM and we have a
number of 400G partitions coming<BR>> off that, I made a snapshot and ran
fsck -yn on it with the following<BR>> output:<BR>><BR>> fsck 1.35
(28-Feb-2004)<BR>> e2fsck 1.35 (28-Feb-2004)<BR>> Pass 1: Checking
inodes, blocks, and sizes<BR>> Inode 2392655 has illegal block(s).
Clear? no<BR>><BR>> Illegal block #9 (4101620032) in inode
2392655. IGNORED.<BR>> Inode 2392655, i_blocks is 672, should be
664. Fix? no<BR><BR></DIV>Is there any chance that some other node on
the san has this lun<BR>mounted, or is writing to it?<BR><FONT
color=#888888><BR>-Eric<BR></FONT>
<DIV>
<DIV></DIV>
<DIV
class=h5><BR>_______________________________________________<BR>Ext3-users
mailing list<BR><A
href="mailto:Ext3-users@redhat.com">Ext3-users@redhat.com</A><BR><A
href="https://www.redhat.com/mailman/listinfo/ext3-users"
target=_blank>https://www.redhat.com/mailman/listinfo/ext3-users</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>Sponser and operater: Linux monitoring solution: <A
href="http://admon.org">http://admon.org</A> <BR></BLOCKQUOTE></BODY></HTML>