<!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.2900.2180" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=259225101-23112004>I have a 1 TB ext3
filesystem mounted via iscsi on a redhat 9 system w/ kernel version -
2.4.20-30.9. I'm not sure when it happened, but today there appears to be
about 7,000 files (600GB) missing. The output from df implies that
the files are still there. It shows 861 GB utilized. But du shows
only 300 GB of data. I'm sure that there are no processes holding onto
deleted files because I have unmounted/mounted the filesystem several times,
synced, etc. Here's an excerpt from e2fsck -nf /dev/sdf
...</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=259225101-23112004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=259225101-23112004>e2fsck 1.32
(09-Nov-2002)<BR>Pass 1: Checking inodes, blocks, and sizes<BR>Inode 674 has
illegal block(s). Clear? no</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=259225101-23112004>Illegal block #32780
(2552928151) in inode 674. IGNORED.<BR>Illegal block #32781 (443979519) in
inode 674. IGNORED.<BR>Illegal block #32782 (2730682564) in inode
674. IGNORED.<BR>Illegal block #32783 (1341333000) in inode 674.
IGNORED.<BR>Illegal block #32784 (864228082) in inode 674.
IGNORED.<BR>Illegal block #32785 (1637408843) in inode 674.
IGNORED.<BR>Illegal block #32786 (2702337062) in inode 674.
IGNORED.<BR>Illegal block #32787 (399755839) in inode 674.
IGNORED.<BR>Illegal block #32788 (2350927161) in inode 674.
IGNORED.<BR>Illegal block #32789 (972130738) in inode 674.
IGNORED.<BR>Illegal block #32790 (726004907) in inode 674. IGNORED.<BR>Too
many illegal blocks in inode 674.<BR>Clear inode? no</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=259225101-23112004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=259225101-23112004>[ This message
basically repeats itself and eventually e2fsck errors out with...
]</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=259225101-23112004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=259225101-23112004>Error while
iterating over blocks in inode 675: Illegal indirect block found<BR>e2fsck:
aborted</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=259225101-23112004>/dev/sdf: **********
WARNING: Filesystem still has errors **********</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=259225101-23112004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=259225101-23112004>Things look pretty
grim right now. As soon as I run e2fsck -p, these inodes will be deleted
and I will lose data, correct? I suspect the cause of this issue was
multiple hosts mounting this filesystem r/w. Does anyone know of any
method that could be used to recover this data? Any help would be greatly
appreciated.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=259225101-23112004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=259225101-23112004> -
Jeff</SPAN></FONT></DIV></BODY></HTML>