linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Vic" <lvm@beer.org.uk>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Fun and games with mirroring
Date: Tue, 22 May 2012 15:50:12 +0100 (BST)	[thread overview]
Message-ID: <53772.172.16.0.29.1337698212.squirrel@beer.org.uk> (raw)


Hi All.

Forgive me if this has been dealt with before - I couldn't find a search
tool for the archives...

I've just had a play with LVM mirroring. It appears to have a rather
serious usability issue.

I added a new drive to my system, created a PV, then used lvconvert -m1 to
mirror my various volumes. Sure enough, the new PV eventually contained my
data. As far as I knew, I now had failure resilience at the LVM layer.

So I simulated a failure - I powered down the machine and removed the new
drive. And then it all went wrong.

The boot sequence went through Grub, then failed. It could not find my
root FS. Swapping drives to the other one did exactly the same - neither
disk from my "mirror" was bootable.

After a bit of poking at it, I found that the LVM system would not start
the VG with a missing PV. Even after starting it manually (and mounting
it, and looking at it) at a recovery shell (dracut? I'm not sure), I still
couldn't get the machine booted.

I fixed it eventually by booting into a LiveUSB. The only thing I could
get to work was to vgreduce --removemissing --force each of the disks.
This is clearly not the sort of thing we ought to be doing for something
as simple as a disk failure...

So it is that using LVM mirrors, we end up with the machine being rendered
unbootable if either disk fails. That can't be right, can it?

Vic.

p.s. The reason I want to do this with LVM mirrors rather than MD RAID is
that this is potentially a very useful way of grabbing a backup snapshot
of a machine prior to some risky operation - it allows me to "fork" a
machine onto two sets of media. But if it leaves the result unbootable,
that's something of a problem...

             reply	other threads:[~2012-05-22 14:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 14:50 Vic [this message]
2012-05-22 15:27 ` [linux-lvm] Fun and games with mirroring Les Mikesell
2012-05-22 15:29   ` Vic
2012-05-22 16:00     ` Bryn M. Reeves
2012-05-22 16:40       ` Vic
2012-05-22 19:24         ` Brassow Jonathan
2012-05-22 19:59           ` Vic
2012-05-23  8:52             ` Bryn M. Reeves
2012-05-23 10:02             ` Zdenek Kabelac
2012-05-23 15:16             ` Brassow Jonathan
2012-05-23  8:54         ` Bryn M. Reeves
2012-05-23 15:21           ` Les Mikesell
2012-05-23 15:36             ` Bryn M. Reeves
2012-05-23 17:03               ` Les Mikesell
2012-05-23 17:24                 ` Bryn M. Reeves
2012-05-23 18:00                   ` Les Mikesell
2012-05-23 18:32                     ` Stuart D Gathman
2012-05-23 19:07                       ` Les Mikesell
2012-05-23 22:39                         ` Stuart D Gathman
2012-05-22 17:57 ` Stuart D Gathman
2012-05-22 18:39   ` tariq wali
2012-05-23 22:44     ` 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=53772.172.16.0.29.1337698212.squirrel@beer.org.uk \
    --to=lvm@beer.org.uk \
    --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).