From: Julie Ashworth <ashworth@berkeley.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LV mirror extents on same physical device
Date: Sun, 23 Feb 2014 20:29:04 -0800 [thread overview]
Message-ID: <20140224042904.GA13974@localhost.localdomain> (raw)
In-Reply-To: <CAAMCDeeR9QnRp=v724QRfPjtmq29=ZH3kyU0EoN++=0VmL-8HQ@mail.gmail.com>
On 23-02-2014 21.29 -0600, Roger Heflin wrote:
> This indicates that it "worked" that way on some versions rhel5 but
> does not work that way on rhel6 in a number of versions.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=594525
>
> I would suspect depending on exactly what version you are using that
> it is a bug.
>
> I know up to at least 5.7 there are some bad LVM bugs when you are
> doing abnormal things (mirroring, pvmoves with lv with multiple
> extents), there are probably other bugs I don't know about.
>
> I would suggest unmirroring it, and just doing a straight pvmove to
> the new device, mirroring it in the middle would just appear to
> complicate things.
---end quoted text---
Thank you.
It's possible to specify where the extents should be located, i.e.
The following command creates a mirrored logical volume with a single mirror. The volume is 500 megabytes in size, it is named mirrorlv, and it is carved out of volume group vg0. The first leg of the mirror is on device /dev/sda1, the second leg of the mirror is on device /dev/sdb1, and the mirror log is on /dev/sdc1.
lvcreate -L 500M -m1 -n mirrorlv vg0 /dev/sda1 /dev/sdb1 /dev/sdc1
(from http://linux-satya.blogspot.com/2010/09/logical-volume-manager.html)
I regret not doing this. Oh well. At this point, I haven't decided if I should convert to linear LV, or add aother mirror on /dev/md2.
Thanks again for the heads-up about the bug.
best,
Julie
prev parent reply other threads:[~2014-02-24 4:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 7:14 [linux-lvm] LV mirror extents on same physical device Julie Ashworth
2014-02-22 10:12 ` emmanuel segura
2014-02-24 18:56 ` Julie Ashworth
2014-02-24 21:51 ` Julie Ashworth
2014-02-25 11:18 ` emmanuel segura
2014-02-25 11:19 ` emmanuel segura
2014-02-22 10:37 ` James Hawtin
2014-02-22 17:08 ` Julie Ashworth
2014-02-24 1:59 ` John Stoffel
2014-02-24 3:20 ` Julie Ashworth
2014-02-24 2:16 ` Roger Heflin
2014-02-24 3:03 ` Roger Heflin
2014-02-24 3:12 ` Julie Ashworth
2014-02-24 3:13 ` Julie Ashworth
2014-02-24 3:29 ` Roger Heflin
2014-02-24 4:29 ` Julie Ashworth [this message]
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=20140224042904.GA13974@localhost.localdomain \
--to=ashworth@berkeley.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).