All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robb Walker <rwalker@DRWHoldings.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm thin provisioning snapshots and btrfs
Date: Tue, 23 Sep 2014 01:06:26 +0000	[thread overview]
Message-ID: <1411434386471.62907@DRWHoldings.com> (raw)
In-Reply-To: <5420AA80.8060801@redhat.com>

Thanks for the response and insight!
I will try to manipulate sequentially/mutually exclusively as in making changes when only one is online/active
I have had a screen session open on ttyS1 and don't recall a flurry of concerning console messages, but will double check, unless you meant they, btrfs developers, should have this type of issue burble up as a kernel message.
I'll probably give a post to btrfs with your insight listed and see what they say as well

thanks and regards


________________________________________
From: linux-lvm-bounces@redhat.com <linux-lvm-bounces@redhat.com> on behalf of Zdenek Kabelac <zkabelac@redhat.com>
Sent: Monday, September 22, 2014 6:02 PM
To: LVM general discussion and development
Subject: Re: [linux-lvm] lvm thin provisioning snapshots and btrfs

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

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
This e-mail and any attachments may contain information that is confidential and proprietary and otherwise protected from disclosure. If you are not the intended recipient of this e-mail, do not read, duplicate or redistribute it by any means. Please immediately delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail or any attachments. The DRW Companies make no representations that this e-mail or any attachments are free of computer viruses or other defects.

      reply	other threads:[~2014-09-23  1:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 23:10 [linux-lvm] lvm thin provisioning snapshots and btrfs Robb Walker
2014-09-22 22:15 ` Robb Walker
2014-09-22 23:02   ` Zdenek Kabelac
2014-09-23  1:06     ` Robb Walker [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=1411434386471.62907@DRWHoldings.com \
    --to=rwalker@drwholdings.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.