All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rickard Olsson <richie@webhackande.se>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] removing a bad HD
Date: Wed Oct  8 02:24:02 2003	[thread overview]
Message-ID: <3F83BB32.7060308@webhackande.se> (raw)
In-Reply-To: <20031007175710.B25658@crusaders.no>

Trond Michelsen wrote:

> 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?

It's possible that Heinz or one of the other gurus know of a way, but I 
don't. If pvmove -i can't get past the read errors... Theoretically, you 
could be able to hexedit the LVM metadata but I really don't want to 
read about that in the news afterwards, if you know what I mean.

> 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.

If you have a spare disk to start the new VG with, that's probably a 
good idea for several reasons (fresh filesystem, fresh metadata, the 
ability to check disks offline before adding them to the VG and so on).

I did this too since my old extents were rapidly becoming too small. New 
LVs default to a max size of 2TB, when I originally created mine I 
believe they were 250GB unless specified otherwise.

    / Rickard Olsson,IT-Konsult/
   / Telefon: +46 70 635 01 42/
  / http://www.webhackande.se/

  reply	other threads:[~2003-10-08  2:24 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
2003-10-08  2:24     ` Rickard Olsson [this message]
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=3F83BB32.7060308@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 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.