From: Phillip Susi <psusi@ubuntu.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>,
Anand Jain <Anand.Jain@oracle.com>,
kreijack@inwind.it, MegaBrutal <megabrutal@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: Robert White <rwhite@pobox.com>, Chris Mason <clm@fb.com>
Subject: Re: PROBLEM: #89121 BTRFS mixes up mounted devices with their snapshots
Date: Tue, 02 Dec 2014 14:11:33 -0500 [thread overview]
Message-ID: <547E0EE5.2040504@ubuntu.com> (raw)
In-Reply-To: <547DAF2A.7020902@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/2/2014 7:23 AM, Austin S Hemmelgarn wrote:
> Stupid thought, why don't we just add blacklisting based on device
> path like LVM has for pvscan?
That isn't logic that belongs in the kernel, so that is going down the
path of yanking out the device auto probing from btrfs and instead
writing a mount.btrfs helper that can use policies like blacklisting
to auto locate all of the correct devices and pass them all to the
kernel at mount time.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJUfg7lAAoJENRVrw2cjl5RAakIAKLsIKgjzUO8J/PBBDTmcCQh
IvkEMlQ6ME+Zi7xCKM9p+J5Skcu22zj8w2Ip0s/zNo3ydGorajxehUqtU983l5Hd
VklKOuNGZ0wrOtwCH8IkRt9HUvT3I7982jByi2Uk9jxpRbL/BruaJ4NF+Z9HnvHO
cmMNavcKvwOkYpPHPPbeyjNwWALe/WRZZ2cgsKqs/vB2nakxFntUc1UOsnIMfLJ7
dMF0l9GudoIoNaqRUNoxV1/Lh9MxKx0p9mBK6Pc+V+wLulUyOUSQ6OkUTsznCabk
iUyzX9IYiF83hWO3g+1vxR+GCeYNVGvC/Rj8ZkLSt9Tpi7JH0kbXnq6wKedSfE0=
=Lxfb
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-02 19:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 12:56 PROBLEM: #89121 BTRFS mixes up mounted devices with their snapshots MegaBrutal
2014-12-01 17:27 ` Robert White
2014-12-01 22:10 ` MegaBrutal
2014-12-01 23:24 ` Robert White
2014-12-02 0:15 ` MegaBrutal
2014-12-02 7:50 ` Goffredo Baroncelli
2014-12-02 8:28 ` MegaBrutal
2014-12-02 11:14 ` Goffredo Baroncelli
2014-12-02 11:54 ` Anand Jain
2014-12-02 12:23 ` Austin S Hemmelgarn
2014-12-02 19:11 ` Phillip Susi [this message]
2014-12-03 8:24 ` Goffredo Baroncelli
2014-12-04 3:09 ` Phillip Susi
2014-12-04 5:15 ` Duncan
2014-12-04 8:20 ` MegaBrutal
2014-12-04 13:14 ` Duncan
2014-12-02 19:14 ` Phillip Susi
2014-12-08 0:05 ` Konstantin
2014-12-01 21:45 ` Konstantin
2014-12-02 5:47 ` MegaBrutal
2014-12-02 19:19 ` Phillip Susi
2014-12-03 3:01 ` Russell Coker
2014-12-08 0:32 ` Konstantin
2014-12-08 14:59 ` Phillip Susi
2014-12-08 22:25 ` Konstantin
2014-12-09 16:04 ` Phillip Susi
2014-12-10 3:10 ` Anand Jain
2014-12-10 15:57 ` Phillip Susi
2014-12-08 17:20 ` Robert White
2014-12-08 22:38 ` Konstantin
2014-12-08 23:17 ` Robert White
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=547E0EE5.2040504@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=Anand.Jain@oracle.com \
--cc=ahferroin7@gmail.com \
--cc=clm@fb.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=megabrutal@gmail.com \
--cc=rwhite@pobox.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.