From: jerome lacoste <jerome.lacoste@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: defective RAM: corrupted ext3 FS. How to identify corrupted files/directories?
Date: Fri, 25 Nov 2005 11:34:06 +0100 [thread overview]
Message-ID: <5a2cf1f60511250234p3f00351ah956cb3615e0c1dbe@mail.gmail.com> (raw)
Hi.
My RAM died, and it corrupted my file system. It seems like this
machine just wants to die... [1]
After removing the faulty RAM, I can boot. I made extensive memtest86+ tests.
I now have my home partition mounted as read-only because of said corruption.
I see a bunch of "ext3_readdir: directory xxxx contains a hole at
offset xxxxx" when I try to access some parts of my disk.
I postponed fscking the FS until I have identified the faulty data.
I was thinking of doing a rsync --dry-run against a known working
backup and check the logs. Any better idea? Is there a way to convert
the directory IDs into file paths?
I have around 500 000 files on that partition. It takes time checking them all.
Cheers,
Jerome
[1] http://lkml.org/lkml/2005/2/4/51
next reply other threads:[~2005-11-25 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 10:34 jerome lacoste [this message]
2005-11-26 6:43 ` Willy Tarreau
2005-11-26 8:47 ` Grant Coady
[not found] <5cJ9S-44L-3@gated-at.bofh.it>
2005-11-25 22:49 ` Bodo Eggert
2005-11-28 13:32 ` linux-os (Dick Johnson)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a2cf1f60511250234p3f00351ah956cb3615e0c1dbe@mail.gmail.com \
--to=jerome.lacoste@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®