From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
ttguy1@gmail.com
Subject: Re: [linux-lvm] root: Failed query for merging percentage. Aborting merge
Date: Mon, 10 Apr 2017 12:54:25 +0200 [thread overview]
Message-ID: <5e89719c-2e67-fb6b-50c3-2e4a544a31af@redhat.com> (raw)
In-Reply-To: <CAC=a5kw1oa1w-6OmHe5tuVwtok_qd=tr26pYTk-FK-_+6zf2Zg@mail.gmail.com>
Dne 9.4.2017 v 09:17 Roger Morton napsal(a):
> I wanted to merge a old snap shot (root_snap10) of my root file system back
> into root.
>
>
> LV VG Attr LSize Pool Origin Data% Meta% Move
> Log Cpy%Sync Convert
> home_lv kubuntu-vg rwi-aor--- 1000.00g
> 100.00
> root kubuntu-vg owi-aor--- 50.00g
> 100.00
> root_snap10 kubuntu-vg swi-a-s--- 50.00g root 28.42
> root_snap14 kubuntu-vg swi-a-s--- 50.00g root 0.00
>
In genernal -
Once the merge IS started - you see immediately 'the merged state' and the
blocks are moved in background (they are moved back from COW to origin -
while you already see a device in 'merged-state').
While the merge IS happening you can't merge another LV.
So you need to wait till merge of snap10 is finished (0%).
>
> sudo lvcreate -s -n root_snap10b -L 50G /dev/kubuntu-vg/root
> Snapshots of an origin that has a merging snapshot is not supported
>
> So the system still thinks /dev/kubuntu-vg/root is in the middle of merging.
> Which worries me - my root file system might be in some half and half state
> between two different snapshots
As said there is never 'half and half state' - this would clearly never work
;) you can't see old & new data mixed at the same time.
Regards
Zdenek
next prev parent reply other threads:[~2017-04-10 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 7:17 [linux-lvm] root: Failed query for merging percentage. Aborting merge Roger Morton
2017-04-10 10:54 ` Zdenek Kabelac [this message]
2017-04-10 13:41 ` Roger Morton
-- strict thread matches above, loose matches on Subject: below --
2017-04-11 9:42 Roger Morton
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=5e89719c-2e67-fb6b-50c3-2e4a544a31af@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=ttguy1@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 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).