From: Phillip Susi <psusi@ubuntu.com>
To: 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: Tue, 02 Dec 2014 14:19:22 -0500 [thread overview]
Message-ID: <547E10BA.6000707@ubuntu.com> (raw)
In-Reply-To: <547CE175.6060409@web.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/1/2014 4:45 PM, Konstantin wrote:
> The bug appears also when using mdadm RAID1 - when one of the
> drives is detached from the array then the OS discovers it and
> after a while (not directly, it takes several minutes) it appears
> under /proc/mounts: instead of /dev/md0p1 I see there /dev/sdb1.
> And usually after some hour or so (depending on system workload)
> the PC completely freezes. So discussion about the uniqueness of
> UUIDs or not, a crashing kernel is telling me that there is a
> serious bug.
I'm guessing you are using metadata format 0.9 or 1.0, which put the
metadata at the end of the drive and the filesystem still starts in
sector zero. 1.2 is now the default and would not have this problem
as its metadata is at the start of the disk ( well, 4k from the start
) and the fs starts further down.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJUfhC6AAoJENRVrw2cjl5RQ2EH/0Z0iCFjOs3e5oGuGqT5Wtlc
rXV8R1EfGSxESK0g6QAe7QIvJu+0CdIgccDp8z3ezfPcm1/YRfBXxXA/Y1Wl4hqw
0wuk3bNqMjUmNwIFjEZCkgOSn4Whuppbh3hOOVGNropr4cwd84GP1Cr2vrzwYnkm
If1I3RTaBhAJRSngkP9X+L5J6zBBjaZLlF4AjC/WP/1bd5vkHpGqnFpRTquCPiNV
9LFWQIB+xYdoRdK2l7huS2jQ5kfw+qLZUQO17dU3fcicwwNk56V4HcLEPg9nx9es
pxJo9BAWmQXDpeMcCL4eFECoeAhn0IXoaXb363mmpq11qyYj73r3FzhNQ+ALzPY=
=U65Z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-02 19:19 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 [this message]
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=547E10BA.6000707@ubuntu.com \
--to=psusi@ubuntu.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 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.