From: Ross Boylan <ross@biostat.ucsf.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] dealing with a failing drive (esp pvmove)
Date: Wed, 22 Dec 2010 11:55:16 -0800 [thread overview]
Message-ID: <1293047716.10784.28.camel@corn.betterworld.us> (raw)
I have a volume group made from 3 partitions on 2 different physical
disks. One of the disks is failing. I have a new disk connected via
USB; it is large but a bit slow (5400RPM, though the USB might be
temporary). It is large enough to hold the entire contents of the
existing VG.
I am looking for suggestions about how to approach this. The pvmove
command looks promising, but the docs warn that things are in a delicate
state during the migration (and advise backups). Since it seems almost
certain there will be I/O errors on the old drive, I'm not sure if
pvmove is a good idea. Is it?
Alternately, I could do a file system level rsync, but I would probably
need to boot into an alternate system for the last step and there are
quite a few LVs.
Would any kind of RAID/mirroring be an option? My impression is I need
to set that up on initial creation of the VG.
BTW, any advice on partitioning the new drive? I know I could just use
the whole physical device, but I'm concerned that if I want to boot
using the disk, or install another (non-Linux) OS that I'll need more
traditional partitions on the drive. My first cut was to create a GPT
partitioning scheme with a 1G blank paritition and partition 2 holding
the rest of the 2TB for LVM. Linux is my primary OS.
Thanks.
Ross Boylan
next reply other threads:[~2010-12-22 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 19:55 Ross Boylan [this message]
2010-12-22 20:38 ` [linux-lvm] dealing with a failing drive (esp pvmove) Richard Shaw
2010-12-23 3:17 ` Stuart D. Gathman
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=1293047716.10784.28.camel@corn.betterworld.us \
--to=ross@biostat.ucsf.edu \
--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).