From: Rene Gallati <lvm@gallati.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] disaster recovery
Date: Sun Jan 26 12:32:01 2003 [thread overview]
Message-ID: <3E342978.9020708@gallati.net> (raw)
In-Reply-To: <3E3151C1.7070409@gallati.net>
Rene Gallati wrote:
> I'm wondering if I have all the tools required to attemp to recover the
> remaining data from the good drive?
[..]
Having recieved no answer I just stepped ahead and tried it in another
system I set up only for the recovery process. First I tried to patch a
stock SuSE 8.1 kernel (2.4.19-4GB) which failed as expected. Then I went
and fetched a vanilla 2.4.20 from my local kernel.org mirror - and that
failed miserably too !
Looked into device-mapper's directory structure and decieded to fetch a
2.4.19 vanilla which finally succeeded. You really might want to add
that information to device-mapper's README or INSTALL - especially since
people who have hosed LV's are probably going to use LVM2 the most.
So out of the 4LVs that were in the VG, I could get out the data from
two smaller ones that were completely within the first still good disk.
However the other two I couldn't mount. One I did expect but the other
not. One out of those two LVs was spanning the disks, and the latter
disk is now gone for good. Anyone knows a nice trick to get reiserfs
allowing me to mount that LV anyway and get out what's left ?
Or am I completely lost there?
Thanks for all answers in advance.
CU
Ren�
btw. recovering from hd failure is really cool when they turn off your
net connectivity because of some MS-SQL worm... :-/
prev parent reply other threads:[~2003-01-26 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 8:47 [linux-lvm] disaster recovery Rene Gallati
2003-01-26 12:32 ` Rene Gallati [this message]
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=3E342978.9020708@gallati.net \
--to=lvm@gallati.net \
--cc=linux-lvm@sistina.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