From: "Vic" <lvm@beer.org.uk>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Fun and games with mirroring
Date: Tue, 22 May 2012 17:40:36 +0100 (BST) [thread overview]
Message-ID: <54198.172.16.0.29.1337704836.squirrel@beer.org.uk> (raw)
In-Reply-To: <4FBBB834.302@redhat.com>
>> You can do it to a box that hasn't been set up with mdadm...
>
> Sure but you will need LVM set up.
I always have.
> In that case, why not use LVM's snapshot capabilities?
Because that doesn't do what I want.
I'm not looking to have a LVM snapshot. I'm looking to have a duplicate
disk. This allows me to experiment on one, whilst keeping the other safe.
Alternatively, it allows me to migrate from one disk to another without
too much risk - before anyone points me at pvmove, I lost a filesystem
when that fell over on a live machine once :-(
> You might find this works better for this particular use of mirroring
> but you can also try the --splitmirrors option to the lvconvert
> command (but it will be less efficient since it will take a
> block-by-block copy of the origin during the lvconvert -m1 rather than
> just recording changes as a snapshot would). Mirror splitting was
> added in 2.02.88 (about nine months old).
--splitmirrors would seem to do what I'm after *except* that it will leave
the mirror unbootable without further attention (the machine won't boot
with the wrong name on the LVs)
> I've found that dracut doesn't always handle LVM errors particularly
> gracefully (in particular if there is a problem the dracut main loop
> appears to reset state after leaving the interactive shell so even if
> you do fix the problem such that the system could continue to boot it
> will just fail in the same way again) and by the sound of it this
> could be improved for your case too.
This is true - but sorta misses the point; a LV mirror is not a LV mirror
if it won't activate. Adding a mirror means that a faliure of *either*
side renders the whole unusable.
> Ideally you'd want the initramfs scripts to carry out the same actions
> as the defined mirror repair policy during startup (or to invoke
> lvconvert --repair to do the same).
Well, we can call it Somebody Else's Problem, or perhaps LVM should be
able to use a broken mirror - that's how every other mirror system works,
and is generally the very reason for having a mirror at all. I consider
this to be a bug within LVM.
Vic.
next prev parent reply other threads:[~2012-05-22 16:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:50 [linux-lvm] Fun and games with mirroring Vic
2012-05-22 15:27 ` Les Mikesell
2012-05-22 15:29 ` Vic
2012-05-22 16:00 ` Bryn M. Reeves
2012-05-22 16:40 ` Vic [this message]
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=54198.172.16.0.29.1337704836.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).