From: Trond Michelsen <mike@crusaders.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] removing a bad HD
Date: Tue Oct 7 11:06:01 2003 [thread overview]
Message-ID: <20031007175710.B25658@crusaders.no> (raw)
In-Reply-To: <3F8105B3.1040506@webhackande.se>; from richie@webhackande.se on Mon, Oct 06, 2003 at 06:04:05AM +0000
On Mon, Oct 06, 2003 at 06:04:05AM +0000, Rickard Olsson wrote:
> Trond Michelsen wrote:
>
> > Recently a harddrive in my LVM started giving me read-errors, so
> > naturally I wanted to replace the drive with a new one.
>
> I recently went through this (with the added complication of some bad
> metadata) and you have a few options.
>
> The best one may be to use dd (with NOERROR) to raw copy the contents
> from the old disk to a new one of the same size and then use the new one
> when doing the pvmove.
>
> Another path is to upgrade to LVM2 (you may have to do this anyway, I
> needed some functionality in the LVM2 pvcreate to pull my stunt off) and
> use the "partial" feature. I haven't tried this myself.
>
> There are more details of my tribulations just a few weeks back in the
> list archives, but feel free to ask if there's something missing (I had
> some private conversations with Heinz on the topic as well).
Thanks, but is it really necessary to copy the PE at all? It's broken,
and I don't care about that 8MB of data. Isn't it possible to just
reassign the LE that's mapped to the broken PE to a completely empty PE
at some other disk?
At the moment I'm a bit tempted to just set up a new VG, and migrate
data from the old VG file by file, disk by disk.
--
// Trond Michelsen
\X/ mike@crusaders.no
next prev parent reply other threads:[~2003-10-07 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 14:17 [linux-lvm] removing a bad HD Trond Michelsen
2003-10-06 1:05 ` Rickard Olsson
2003-10-07 11:06 ` Trond Michelsen [this message]
2003-10-08 2:24 ` Rickard Olsson
2003-10-08 11:17 ` Trond Michelsen
2003-10-08 12:30 ` Rickard Olsson
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=20031007175710.B25658@crusaders.no \
--to=mike@crusaders.no \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.