From: Zdenek Kabelac <zkabelac@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] blkid_wiping breaks snapshots
Date: Mon, 10 Feb 2014 09:33:20 +0100 [thread overview]
Message-ID: <52F88ED0.8030201@redhat.com> (raw)
In-Reply-To: <20140208005550.6b7e134d@leda.localdomain>
Dne 8.2.2014 00:55, Christian Hesse napsal(a):
> Christian Hesse <list@eworm.de> on Sat, 2014/02/08 00:36:
>> Hello everybody,
>>
>> I think I nailed it down with git bisect. My first bad commit is:
>>
>> 75628f341ad38b68aae33eae0b5700be2a6e5769
>> configure: enable blkid_wiping by default if the blkid library is present
>>
>> Looks like this wipes data that is still needed... Building a package with
>> '--disable-blkid_wipe' now to verify on another system.
>
> Uh, this only helps part of...
>
> I changed my test setup and used writable snapshots. After that I got:
>
> WARNING: DM_snapshot_cow signature detected on /dev/cvg/snap-home at
> offset 0. Wipe it? [y/n]
>
> (see https://bbs.archlinux.org/viewtopic.php?id=176504 for another report)
>
> Looks like disabling blkid_wiping fixes this. My snapshot corruption still
> occurs though. :-/
> Bad thing about it is that the corruption does not occur reliable when doing
> simple tests in 'git bisect'... Out of ideas for now - Will go to bed now.
Now this was helpful, I guess I think what is going on.
Zdenek
next prev parent reply other threads:[~2014-02-10 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 13:27 [linux-lvm] lvm2 2.02.105 breaks snapshots Christian Hesse
2014-02-04 8:55 ` Christian Hesse
2014-02-04 16:47 ` Zdenek Kabelac
2014-02-06 14:48 ` Christian Hesse
2014-02-07 13:14 ` Christian Hesse
2014-02-07 23:36 ` [linux-lvm] blkid_wiping breaks snapshots (was: lvm2 2.02.105 breaks snapshots) Christian Hesse
2014-02-07 23:55 ` Christian Hesse
2014-02-10 8:33 ` Zdenek Kabelac [this message]
2014-02-10 9:30 ` [linux-lvm] blkid_wiping breaks snapshots Christian Hesse
2014-02-10 12:20 ` Zdenek Kabelac
2014-02-10 13:48 ` Christian Hesse
2014-02-10 14:12 ` Peter Rajnoha
2014-02-10 14:37 ` Christian Hesse
2014-02-10 15:56 ` Zdenek Kabelac
2014-02-10 18:15 ` Peter Rajnoha
2014-02-10 19:50 ` Zdenek Kabelac
2014-02-18 8:15 ` Christian Hesse
2014-02-18 8:27 ` Zdenek Kabelac
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=52F88ED0.8030201@redhat.com \
--to=zkabelac@redhat.com \
--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 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.