From: Rickard Olsson <richie@webhackande.se>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: One PV destroyed - now the whole VG isn't working anymore
Date: Tue Nov 4 01:47:01 2003 [thread overview]
Message-ID: <3FA7591C.2080105@webhackande.se> (raw)
In-Reply-To: <000001c3a255$1f5f3940$7801a8c0@asuncion>
Samuel Leuthold wrote:
> So can i release the third disk from the LV, reformat and rebind into it
> without loosing the data on disk1 and 2??
Yes. But, if you are using striping instead of simple concatenation, you
are, as the saying goes, toast.
However, it may be possible to salvage most of the data from the third
disk too.
Method #1.
Use dd conv=noerror to raw copy data off the bad disk to a fourth,
good disk. Swap the bad disk for the new one.
Method #2.
If there's free space on the other two disks (or you can add a fourth
disk), you can try pvmove --ignore_read_errors to move as many
extents as possible off the bad disk onto the good ones.
> And what about the reiser? Is it
> consistent after this "hack"??
No, in all cases you will need to run reiserfsck, most likely with the
-rebuild-tree option. But seeing as your disk has badblocks, your FS is
already in a bad state.
> Can i do it with these commands??
If your metadata is intact, you won't need most of that example. You can
search the list archive for my conversation with Heinz a little over a
month or so ago, we went through this exact thing. :-)
> Whats the meaning of
> the "0" in storage\0 ??
Think of it as an end-of-line character (it's a null-terminated string).
/ Rickard Olsson,IT-Konsult/
/ Telefon: +46 70 635 01 42/
/ http://www.webhackande.se/
next prev parent reply other threads:[~2003-11-04 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031103134603.407.73496.Mailman@hermes.sistina.com>
2003-11-03 15:56 ` [linux-lvm] Re: One PV destroyed - now the whole VG isn't working anymore Samuel Leuthold
2003-11-04 1:47 ` Rickard Olsson [this message]
2003-11-04 2:22 ` Re[2]: " Spam
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=3FA7591C.2080105@webhackande.se \
--to=richie@webhackande.se \
--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