From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V2][BTRFS-PROGS] Don't use LVM snapshot device
Date: Fri, 5 Dec 2014 07:26:05 +0000 (UTC) [thread overview]
Message-ID: <pan$67e00$edffae8a$cb013d3$4a1bb73d@cox.net> (raw)
In-Reply-To: 1417718382-6753-1-git-send-email-kreijack@inwind.it
Goffredo Baroncelli posted on Thu, 04 Dec 2014 19:39:37 +0100 as
excerpted:
> To check if a device is a LVM snapshot, it is checked the 'udev'
> device property 'DM_UDEV_LOW_PRIORITY_FLAG' . If it is set to 1,
> the device has to be skipped.
>
> As consequence, btrfs now depends also by the libudev.
Not being a coder I gotta ask...
How does this patch deal with mdev (busybox) or static dev instead of
udev? Does it gracefully degrade to legacy LVM-agnostic behavior?
Meanwhile, just requiring libudev is certain to bring some pretty zealous
opposition from the anti-systemd/anti-udev camp. I like the goal, but
that better be an optional dep unless we're deliberately stepping into
that debate, because that's exactly what we'd be doing.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-12-05 7:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 18:39 [PATCH V2][BTRFS-PROGS] Don't use LVM snapshot device Goffredo Baroncelli
2014-12-04 18:39 ` [PATCH 1/5] Avoid to consider lvm snapshots when scanning devices Goffredo Baroncelli
2014-12-08 2:02 ` Qu Wenruo
2014-12-08 14:58 ` Goffredo Baroncelli
2014-12-09 0:32 ` Qu Wenruo
2014-12-09 10:27 ` David Sterba
2014-12-09 18:19 ` Goffredo Baroncelli
2014-12-04 18:39 ` [PATCH 2/5] 'btrfs device scan' skips lvm snapshots Goffredo Baroncelli
2014-12-04 18:39 ` [PATCH 3/5] Update 'btrfs device scan' man page Goffredo Baroncelli
2014-12-04 18:39 ` [PATCH 4/5] Add reference to BTRFS_SKIP_LVM_SNAPSHOT environment variable Goffredo Baroncelli
2014-12-04 18:39 ` [PATCH 5/5] Abort in case of device uuid conflict Goffredo Baroncelli
2014-12-05 7:26 ` Duncan [this message]
2014-12-05 18:39 ` [PATCH V2][BTRFS-PROGS] Don't use LVM snapshot device Goffredo Baroncelli
2014-12-08 15:30 ` Phillip Susi
2014-12-08 17:36 ` Goffredo Baroncelli
2014-12-08 18:17 ` Phillip Susi
2014-12-08 19:22 ` Robert White
2014-12-10 7:52 ` Anand Jain
2014-12-10 18:40 ` Goffredo Baroncelli
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='pan$67e00$edffae8a$cb013d3$4a1bb73d@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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.