From: Ken Bass <daytooner@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Rebuilding ext4 filesystem on an LV
Date: Wed, 7 Jul 2010 19:46:36 -0700 [thread overview]
Message-ID: <AANLkTinATF8nv02K4F0SQiR1OGg0rZ3P5lpsITcB-RYb@mail.gmail.com> (raw)
In-Reply-To: <20100706161745.GB31734@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]
On Tue, Jul 6, 2010 at 9:17 AM, Malahal Naineni <malahal@us.ibm.com> wrote:
> If everything went right, he should have the new PV in the LV, but looks
> like something failed while activating the LV. Run 'dmsetup table' to
> find out if the LV currently has new PV or old PV. You need
> device-mapper knowledge for this.
>
> I will have to try that out. Will let you know.
>
> The best course of action would have been 'reading what ever data
> available' from old disk to new disk. If the disk is absolutely
> thrashed, then zero'ing the new PV may be better.
>
>
I did try to read anything I could out of the old disk. I do believe there
is still some data on it that wasn't trashed. The problem is how to find it
and reconstruct it without any of the LVM or ext4 filesystem information
(as I said, I couldn't find any superblocks). Are there any utilities to do
something like that?
Then there are the remaining drives that weren't affected. Unfortunately
without the first drive, I can't get to anything on the others. Or can I?
I've tried several things, but I haven't found anything that works. Are
there any utilities for that?
I found an app that will scan a disk looking for lost partitions, and then
looking for various filesystems within them - and it does recognize ext2/3.
It will then recover files at that point. But it runs on windows (won't work
with wine), and it is taking several days to scan the entire drive (100G).
Also, there could be several hundred files, and trying to identify all of
those (possibly) recovered files would be excrutiating :-( .
As always, thx everyone for your help.
ken
[-- Attachment #2: Type: text/html, Size: 2261 bytes --]
next prev parent reply other threads:[~2010-07-08 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 1:30 [linux-lvm] Rebuilding ext4 filesystem on an LV Ken Bass
2010-07-05 5:54 ` Bryan Whitehead
2010-07-05 8:52 ` Ken Bass
2010-07-05 10:06 ` Bryan Whitehead
2010-07-05 15:39 ` Ken Bass
2010-07-05 18:27 ` Stuart D. Gathman
2010-07-05 21:16 ` Ken Bass
2010-07-06 16:17 ` Malahal Naineni
2010-07-08 2:46 ` Ken Bass [this message]
2010-07-08 18:59 ` Malahal Naineni
2010-07-08 19:06 ` Stuart D. Gathman
2010-07-08 19:13 ` Stuart D. Gathman
2010-07-12 18:57 ` Ken Bass
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=AANLkTinATF8nv02K4F0SQiR1OGg0rZ3P5lpsITcB-RYb@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).