From: Richard van den Berg <richard@vdberg.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Does pv failure effect whole vg?
Date: Thu, 21 Jun 2007 09:43:30 +0200 [thread overview]
Message-ID: <467A2C22.6030503@vdberg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0706201722500.12479-100000@bmsred.bmsi.com>
Stuart D. Gathman wrote:
> If the system truly won't boot with a failed disk, that kind of adds another
> reason why current LVM mirroring support is useless.
>
> If you build your VG on raid (md devices or hardware), you solve
> the problem for now.
>
That is what I am doing. The test I did was:
lv00 and lv01 are part of vg00 which consists of /dev/md2 and /dev/sdb3
When booting from cdrom (systemrescuecd) md2 failed to come up, so vg00
did not come up. I then manually brought up md2 and split the vg, and
added sda3 in the mix:
lv00 is part of vg00 which consists of /dev/md2
lv01 is part of vg01 which consists of /dev/sdb3 and /dev/sda3
At the next reboot from cdrom vg01 came up fine, vg00 did not.
At least after the split if sda or sdb fails, md2 should still come up
and so should vg00, but I will loose vg01. Keeping all lvs in vg00
would have given me an unbootable system after 1 disk failure.
Sincerely,
Richard van den Berg
PS: I still think it sucks that I could not split the vg online.
next prev parent reply other threads:[~2007-06-21 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 6:39 [linux-lvm] Does pv failure effect whole vg? Richard van den Berg
2007-06-20 17:57 ` Richard van den Berg
2007-06-20 21:36 ` Stuart D. Gathman
2007-06-21 7:43 ` Richard van den Berg [this message]
2007-06-21 14:45 ` Stuart D. Gathman
2007-06-21 16:31 ` Richard van den Berg
2007-06-22 3:14 ` f-lvm
2007-06-24 15:43 ` Nix
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=467A2C22.6030503@vdberg.org \
--to=richard@vdberg.org \
--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).