All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason Warr" <jason@warr.net>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Anatoly Pugachev <matorola@gmail.com>
Subject: Re: [linux-lvm] Raid1 -> linear conversion = destroyed data
Date: Mon, 08 Dec 2014 14:59:59 -0600	[thread overview]
Message-ID: <op.xqkhx9gjae9kta@comodus> (raw)
In-Reply-To: <CADxRZqyi7Ybowtm8YXErwZY7o3NjSi7XELBSnp8xk0mKo4vOOw@mail.gmail.com>

On Mon, 08 Dec 2014 02:30:06 -0600, Anatoly Pugachev <matorola@gmail.com>  
wrote:

> On Mon, Dec 8, 2014 at 12:24 AM, Phillip Susi <psusi@ubuntu.com> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> On 12/05/2014 05:12 AM, Anatoly Pugachev wrote:
>> > Phillip,
>> >
>> > can you please paste the commands you've used to convert the
>> > volume? I don't have ubuntu , but rhel7 manual page for lvconvert,
>> > example section is pretty clear on how to convert back to flat
>> > (-m0) volume and what physical device you remove from logical
>> > volume, quote:
>> >
>> >
>> > Converts mirror logical volume "vg00/lvmirror1" to linear, freeing
>> > physical extents from /dev/sda:
>> >
>> > lvconvert -m0 vg00/lvmirror1 /dev/sda
>>
>> I simply used lvconvert -m0 vg/lv.  I did not think I would need to
>> specify which leg should be kept; obviously it should be the one
>> currently in use rather than the out of date copy.
>
>
> I wonder how many more people would lost their data before there would
> be changes to lvconvert -m0 to require specification of physicalVolume
> instead of optional requirement.
>

I may have missed part of the discussion but in order to fully understand  
what is going on I'd like to know what arguments you used when you issued  
the "lvconvert --splitmirrors" command.  There are several options to it  
that can influence what happens to the mirror members.

The best way I know of to get that is from the /etc/lvm/archive/ files for  
the volume group in question.  Those contain the maps for the volume  
group.  A new map version is created in that directory after every command  
that modifies the volume group.  Each map contains a "description" line  
that shows the command that was run making the changes.  The map does not  
include the changes as it is meant to be used as a reference to the  
configuration before the change.

If you only want to send the commands as pulled from the archive maps here  
is an example from the system I have been trying to re-create this failure  
scenario on.

[2:root@hostname /root]# grep Created /etc/lvm/archive/test01VG_0000*
/etc/lvm/archive/test01VG_00000-1787228376.vg:description = "Created  
*before* executing 'vgcreate test01VG /dev/sdar /dev/sdas /dev/sdat  
/dev/sdau /dev/sdav /dev/sdaw /dev/sdax'"
/etc/lvm/archive/test01VG_00001-1025082804.vg:description = "Created  
*before* executing 'lvcreate -L50G -m1 --type raid1 test01VG -n test01LV'"
/etc/lvm/archive/test01VG_00002-178937097.vg:description = "Created  
*before* executing 'lvconvert --splitmirrors 1 --name test01LV-M1  
test01VG/test01LV'"

  reply	other threads:[~2014-12-08 21:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 23:07 [linux-lvm] Raid1 -> linear conversion = destroyed data Phillip Susi
2014-12-05 10:12 ` Anatoly Pugachev
2014-12-07 21:24   ` Phillip Susi
2014-12-08  8:30     ` Anatoly Pugachev
2014-12-08 20:59       ` Jason Warr [this message]
2014-12-11  1:15         ` Phillip Susi
2014-12-11  1:50           ` Jason Warr
2014-12-11 14:17             ` Phillip Susi
2014-12-11 14:48               ` Jason Warr
2014-12-15 21:53           ` Phillip Susi
2014-12-11  1:16       ` Phillip Susi

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=op.xqkhx9gjae9kta@comodus \
    --to=jason@warr.net \
    --cc=linux-lvm@redhat.com \
    --cc=matorola@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.