linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Tim Milstead <tim@arabidopsis.info>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] failing hard drive
Date: Thu, 22 Mar 2007 20:58:39 +0000	[thread overview]
Message-ID: <4602EDFF.20301@arabidopsis.info> (raw)
In-Reply-To: <4602A6CA.6050809@redhat.com>

Bryn M. Reeves wrote:

SNIP
>> It would be nice if I could just dd the failing drive onto the new drive
>> and replace it (using linux on a cd) but I have no reason to believe
>> this will work - will it?
>>     
>
> This should work OK, although as usual with backups you want to make
> sure that nothing is writing to the disk while you take the dd - using a
> rescue CD would be fine, or deactivating the volume group before
> starting (but if it includes your root file system then you will need to
> use a rescue CD).
>   
I have made the copy using a rescue CD and an external USB drive. 
Fitting the replacement internally is going to be difficult hence the 
question about doing it this way. Are you sure? I was just worried that 
perhaps LVM looked beyond a simple '/dev/hde' referred to drives in some 
deeper way e.g. serial number, model, make etc.
>   
>> Has anyone got a step by step guide of what to do? I guess I must shrink
>> the filesystem and then whatever that sits on.
>>     
>
> That may work, but you'll need to make enough space within the VG to
> accommodate all the data that is currently stored on the failing hde.
>
> To do this, you first have to shrink file systems from the VG, then
> shrink the logical volumes (LVs) that the file systems are sitting on.
>
> Another option would be to add the new drive to the system and run:
>
> pvcreate /path/to/new/disk
>
> followed by:
>
> vgextend <VG name> /path/to/new/disk
>   
Thanks.
> To temporarily bring the VG up to 10 disks to allow you to remove the
> failing member. You should then find the "pvmove /dev/hde" works as
> expected (assuming the new disk is at least as big as the one you are
> replacing).
>   
Yes, but given the space constraints I'd rather avoid this.
>   
>> This seems to depend on the version of LVM one is running. I have no
>> idea what version comes with Fedora Core 4 or how to find out.
>>     
>
> You'll have lvm2 in FC4, although it's a relatively old version now.
>
> Kind regards,
>
> Bryn.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFGAqbK6YSQoMYUY94RAlG0AJwPGQ60wQ6NyjnouTL9/NsY0fyrwACfdGeS
> pyksRh8UAdGrSwlbm2HJ+tI=
> =39ku
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>   

  reply	other threads:[~2007-03-22 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 15:36 [linux-lvm] failing hard drive Tim Milstead
2007-03-22 15:54 ` Bryn M. Reeves
2007-03-22 20:58   ` Tim Milstead [this message]
2007-03-22 21:31     ` Bryn M. Reeves
2007-03-22 22:33 ` Lamont Peterson
2007-03-23  1:32   ` Stuart D. Gathman
2007-03-26  9:18     ` Tim Milstead

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=4602EDFF.20301@arabidopsis.info \
    --to=tim@arabidopsis.info \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).