From: Michal Soltys <soltys@ziu.info>
To: Bob Bell <b_linuxraid@thebellsplace.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Data loss on MD RAID5 reshape?
Date: Sat, 13 Dec 2008 21:03:15 +0100 [thread overview]
Message-ID: <49441503.5080208@ziu.info> (raw)
In-Reply-To: <20081210192613.GC8354@newbie.thebellsplace.net>
Bob Bell wrote:
> Anyone have anything to add regarding the email below, before I tear the
> drives apart and start over?
>
> On Fri, Dec 05, 2008 at 05:21:32PM -0500, Bob Bell wrote:
>> I've experienced apparent data loss, and hoping someone out there can
>> help rescue my data, or at least tell me what went wrong so that I
>> don't have a repeat event. I first asked this question on linux-lvm,
>> but the folks there seemed to think it pertained more to RAID than to
>> LVM.
>>
>> I was setting up a new server running Ubuntu's Hardy Heron release.
>> `uname -a` reports:
>> Linux sherwood 2.6.24-16-server #1 SMP Thu Apr 10 13:58:00 UTC 2008
>> i686 GNU/Linux
>>
>> I initially created an md RAID5 device with only two components
>> (matching 320 GB SATA HDDs). I created a single LVM Physical Volume
>> using the entirety of that md device (320 GB), and then created
>> several LVM Logical Volumes for different filesystems (all ext3).
>> This was done using the Ubuntu installer.
[...]
>>
>> Did I do something wrong? Is there anyway to rescue my data? If
>> there's no way of saving the data, I'd at least like to figure out
>> what happened in the first place.
>>
The procedure you did seems allright. I just repeated it with few
GB volumes - and everything worked fine here.
Can you provide any more detailed info ? Such as how command lines
looked like, maybe there was something alarming in the logs, etc.
As for recovering the data - you might try dmsetup directly and create
linear mapped volume, precisely 192KiB from the beginning, and with size
of remaining raid volume, then check the size of the filesystem
(assuming it exists at all ..). Unfortunately that assumes, that the LVs
were not fragmented themselves, and that's quite optimistic assumption
considering your whole procedure (lvresize, and I assume - resize2fs or
equivalent for other filesystems).
Do you have any remaining data from the faulty lvm, in /etc/lvm/backup ?
They could be quite helpful, regarding the positions/segments of all
your old LVs.
Also check vgcfgbackup(8) and vgcfgrestore(8)
next prev parent reply other threads:[~2008-12-13 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 22:21 Data loss on MD RAID5 reshape? Bob Bell
2008-12-10 19:26 ` Bob Bell
2008-12-13 20:03 ` Michal Soltys [this message]
2008-12-15 22:11 ` Neil Brown
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=49441503.5080208@ziu.info \
--to=soltys@ziu.info \
--cc=b_linuxraid@thebellsplace.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).