From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [10.36.7.20] (vpn1-7-20.ams2.redhat.com [10.36.7.20]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s8MN2Pe5004715 for ; Mon, 22 Sep 2014 19:02:26 -0400 Message-ID: <5420AA80.8060801@redhat.com> Date: Tue, 23 Sep 2014 01:02:24 +0200 From: Zdenek Kabelac MIME-Version: 1.0 References: <1410908945365.65274@DRWHoldings.com> <1411424085397.51396@DRWHoldings.com> In-Reply-To: <1411424085397.51396@DRWHoldings.com> Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] lvm thin provisioning snapshots and btrfs Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: LVM general discussion and development Dne 23.9.2014 v 00:15 Robb Walker napsal(a): > Also see the same results on ubu 14.04.1 lvm thin provisioning + btrfs. haven't tried arch 3.16 kernel and tools yet > It's likely btrfs problem that it is not reporting duplicity problem? In lvm2 we try to detect duplicate PVs and report problem and pick one to use. Btrfs needs to do the same - I'd expect some kernel messages about these kind of problems? Snapshot activation is skipped here for a reason. It's upto user/admin to avoid system confusion. So my best advice is - to ensure you do not have active origin & snapshot at the same time - especially when manipulating with btrfs - since it most likely ignore device UUID generated by lvm (and that should be unique) You will need to check disk btrfs identifiers if you need to have active these volumes at the same time. > Robb Walker > Linux/Unix Services > Desk (312)542-2361 ~ Mobile (312)804-6034 > Email: rwalker@drw.com > DRW Holdings, LLC ~ 540 West Madison St. Chicago, IL 60661 > Regards Zdenek