From: Phillip Susi <psusi@ubuntu.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: Konstantin <newsbox1026@web.de>,
MegaBrutal <megabrutal@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: PROBLEM: #89121 BTRFS mixes up mounted devices with their snapshots
Date: Wed, 10 Dec 2014 10:57:00 -0500 [thread overview]
Message-ID: <54886D4C.50100@ubuntu.com> (raw)
In-Reply-To: <5487B991.9080906@oracle.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/9/2014 10:10 PM, Anand Jain wrote:
> In the test case provided earlier who is triggering the scan ?
> grub-probe ?
The scan is initiated by udev. grub-probe only comes into it because
it is looking to /proc/mounts to find out what device is mounted, and
/proc/mounts is lieing.
> But we had to revert, Since btrfs bug become a feature for the
> system boot process and fixing that breaks mount at boot with
> subvol.
How is this? Also are we talking about updating the cached list of
devices that *can* be mounted, or what device already *is* mounted? I
can see doing the former, but the latter should never happen.
> if the device is already mounted, just the device path is updated
> but still the original device will be still in use (bug).
Yep, that is the bug that started all of this.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJUiG1MAAoJENRVrw2cjl5Rm0gIAJ6sq72zKSEfCuCjigknx25T
a97wjtMeb+yeaECc5FfwN7Fm454GSSuj6RFCRVjo3sCgJP3sUEH49syJnvW1QiEP
A5ktXfTpz6/zaeP9DbGPDCiVix0RdsJ6bCjP/8InsASueXOENCpxxmblxrbE4Wxj
Mdz8lu9L8G+fc6btbLLb0N4i0clSiImQds90zTQ1cXihJ/4wUIO3qgq+rruSYMqI
A182FS7NTUQrRcJ/rbcha3dCyD/urbCaRTUztMvTnSs3a7hK5p+SBNbfxEORC6ni
HrRMxpOlgHOTMnL3EHw843OuGv0Us3VqVbuPG3K6L4+G4W1sFxgKEAnLvEbjzAI=
=Vpre
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-10 15:57 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
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 [this message]
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=54886D4C.50100@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=megabrutal@gmail.com \
--cc=newsbox1026@web.de \
/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;
as well as URLs for NNTP newsgroup(s).