From: Ken Bass <daytooner@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] [SOLVED?] rebuilding LV ext4 filesystem
Date: Wed, 21 Jul 2010 11:34:45 -0700 [thread overview]
Message-ID: <AANLkTikwNhMWtusJHicMya9k5IS9geQ17ss4aHurjm4z@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]
Okay, I finally got to do what Stuart D. Gathman suggested. And it worked,
sort of.
The problem: the first PV in my LV started to die, and trashed a big portion
of the beginning of the physical drive - including the partition table,
partition info, and ext4 file structure. All I wanted at that point was to
recover what was on the rest of the other PVs in the LV. But nothing could
interpret whatever data was left. e2fsck, et al, all said they could not
find a superblock, even when I tried ones on the other PVs.
Since that original drive was really dying (SMART was spurting out messages
about that), it was somewhat difficult to read anything off of it. But
Stuart did recommend "dd_rescue" to move whatever it could from the dying
drive to a new drive. Which I did. Turns out that most of the access
problems were at the beginning of the drive (why I don't know). So I
basically copied in reverse, starting at the end of the drive. I did this
mainly hoping to find a valid superblock that I could use to bring back up
the LV and run e2fsck on it.
Long story short: dd_rescue did just that. I found a superblock, and ran
e2fsck to fix all of the problems.
NOW: I am left with a clean ext filesystem, but with about 300GB in
lost+found, and not other files. Just guessing on that amount, since that is
how much was on the LV before the crash. So the next logical and obvious
(and desperate) question is: how to I restore all (or any) of the files
under lost+found?
Most of them (that I am interested in)were either image files (jpg, png,
bmp), ISO images (DVD, CD), music files (mp3, flac, etc), and a few MS
executables. Is there a utiliity that can help restore these files, maybe
scan the lost+found files for these types?
Thanks to all for their help. I hope none of you ever have to go through
this yourself :-).
ken
[-- Attachment #2: Type: text/html, Size: 1915 bytes --]
next reply other threads:[~2010-07-21 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 18:34 Ken Bass [this message]
2010-07-21 18:54 ` [linux-lvm] [SOLVED?] rebuilding LV ext4 filesystem Brian McCullough
2010-07-22 23:32 ` Ken Bass
2010-07-23 2:02 ` Stuart D. Gathman
2010-07-23 2:19 ` Ken Bass
2010-07-23 16:35 ` Stuart D. Gathman
-- strict thread matches above, loose matches on Subject: below --
2010-07-21 20:41 daytooner
2010-07-21 21:34 ` Brian McCullough
2010-07-22 23:12 ` Ken Bass
2010-07-22 23:27 ` Stuart D. Gathman
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=AANLkTikwNhMWtusJHicMya9k5IS9geQ17ss4aHurjm4z@mail.gmail.com \
--to=daytooner@gmail.com \
--cc=linux-lvm@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).