From: Goffredo Baroncelli <kreijack@gmail.com>
To: Phillip Susi <psusi@ubuntu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V2][BTRFS-PROGS] Don't use LVM snapshot device
Date: Mon, 08 Dec 2014 18:36:32 +0100 [thread overview]
Message-ID: <5485E1A0.4030602@gmail.com> (raw)
In-Reply-To: <5485C432.3030307@ubuntu.com>
On 12/08/2014 04:30 PM, Phillip Susi wrote:
> On 12/4/2014 1:39 PM, Goffredo Baroncelli wrote:
[...]
>> 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.
>
> Rather than modify btrfs device scan to link to libudev and ignore the
> caller when commanded to scan a snapshot, wouldn't it be
> simpler/better to just fix the udev rule to not *call* btrfs device
> scan on the snapshot?
I like this approach, but as I wrote before, it seems that
initramfs executes a "btrfs dev scan".... (see my previoue email
'Re: PROBLEM: #89121 BTRFS mixes up mounted devices with their snapshots'
date 2014/12/03 9:34):
$ grep -r "btrfs dev.*scan" /usr/share/initramfs-tools/
/usr/share/initramfs-tools/scripts/local-premount/btrfs: /sbin/btrfs device scan 2> /dev/null
(this is from a debian).
However it has to be pointed out that
fedora doesn't seems to do the same...
I have to investigate a bit....
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2014-12-08 17:35 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 ` [PATCH V2][BTRFS-PROGS] Don't use LVM snapshot device Duncan
2014-12-05 18:39 ` Goffredo Baroncelli
2014-12-08 15:30 ` Phillip Susi
2014-12-08 17:36 ` Goffredo Baroncelli [this message]
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=5485E1A0.4030602@gmail.com \
--to=kreijack@gmail.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=psusi@ubuntu.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