From: Michael Tharp <gxti@partiallystapled.com>
To: linux-btrfs@vger.kernel.org
Subject: Degraded volume silently fails to mount
Date: Mon, 13 Apr 2015 09:51:09 -0400 [thread overview]
Message-ID: <552BC9CD.6090406@partiallystapled.com> (raw)
Hi list,
I've got a 4 disk raid1 volume that has one failed disk. I have so far
been unable to mount it in degraded mode, but the failure is that
"mount" silently does nothing.
# btrfs fi sh
warning devid 2 not found already
Label: 'seneca' uuid: b9da07f5-c0fd-45ad-861b-d1bcad6cbf4c
Total devices 4 FS bytes used 581.71GiB
devid 1 size 931.51GiB used 334.02GiB path /dev/mapper/luks-seneca-1
devid 3 size 931.51GiB used 334.01GiB path /dev/mapper/luks-seneca-3
devid 4 size 931.51GiB used 334.01GiB path /dev/mapper/luks-seneca-4
*** Some devices missing
Btrfs v3.18.1
# mount -t btrfs -o degraded /dev/mapper/luks-seneca-1 /seneca
# echo $?
0
# ls /seneca/
# grep seneca /proc/mounts
# dmesg |tail
[ 84.955467] BTRFS: device label seneca devid 1 transid 1753 /dev/dm-4
[ 87.926347] BTRFS: device label seneca devid 4 transid 1753 /dev/dm-5
[ 107.069109] BTRFS: device label seneca devid 3 transid 1753 /dev/dm-6
[ 195.267046] BTRFS info (device dm-6): allowing degraded mounts
[ 195.267094] BTRFS info (device dm-6): disk space caching is enabled
[ 195.267133] BTRFS: has skinny extents
[ 195.277615] BTRFS warning (device dm-6): devid 2 missing
[ 781.160250] BTRFS info (device dm-6): allowing degraded mounts
[ 781.160270] BTRFS info (device dm-6): disk space caching is enabled
[ 781.160286] BTRFS: has skinny extents
# uname -a
Linux ambrosia.homeslice 3.19.3-200.fc21.x86_64 #1 SMP Thu Mar 26
21:39:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
# btrfs --version
Btrfs v3.18.1
Any ideas?
next reply other threads:[~2015-04-13 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 13:51 Michael Tharp [this message]
2015-04-13 14:07 ` Degraded volume silently fails to mount Hugo Mills
2015-04-13 14:38 ` Michael Tharp
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=552BC9CD.6090406@partiallystapled.com \
--to=gxti@partiallystapled.com \
--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.