Re: EXT3-fs error

[Theodore Tso]

On Thu, Aug 31, 2006 at 11:02:35AM -0700, Richard Amick wrote:
> 
> My question:
> How do I determine what is/was contained in "directory #14058742"?

You can run debugfs on the mounted filesystem and give the command:

debugfs: ls <14058742>

You can figure out its pathname by doing a:

debugfs: cd <14058742>
debugfs: pwd

> Running e2fsck is really not an option right now as this is a
> production server and a very large volume (300GB with 150GB used).

Note though that your filesystem *is* corrupted, and running with
errors (as you are currently doing) can risk further filesystem
corruption leading to data loss --- in the worst case, significant
data loss.  

In this particular case, if the reported corrupted directory entry is
the *only* filesystem corruption, it's not likely that it will cause
any problems, but....  This is the point where sky divers are asked to
sign a liability release waiver that essentially says, "I am about to
do this really silly, dangerous thing of my own free will, and it
could lead to significant injury or DEATH."  It might be safe to sky
dive --- although I've never seen the point of jumping out of a
perfectly good airplane --- but there is risk involved.  Some people
seem to get off on risk, though.  :-)

At the very least, I would recommend doing a full backup of your
system....

					- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/