From: Tomasz Chmielewski <tch@virtall.com>
To: linux-btrfs@vger.kernel.org
Subject: can't mount a newly created fs after reboot
Date: Wed, 12 Jun 2013 20:53:03 +0900 [thread overview]
Message-ID: <20130612205303.308095ca@virtall.com> (raw)
I've created two btrfs fileystems using these commands:
mkfs.btrfs -d raid1 -m raid1 -L btrfs1 /dev/sda5 /dev/sdb5
mkfs.btrfs -d raid1 -m raid1 -L btrfs2 /dev/sdc1 /dev/sdd1
Then, added these to /etc/fstab:
LABEL=btrfs1 /mnt/btrfs1 btrfs noatime,compress-force=zlib 0 0
LABEL=btrfs2 /mnt/btrfs2 btrfs noatime,compress-force=zlib 0 0
I mounted these filesystems with:
mount -a
And enabled quotas:
btrfs quota enable /mnt/btrfs1
btrfs quota enable /mnt/btrfs2
I'm using Linux 3.9.5.
After that I've rebooted and I'm no longer able to mount these two
fileystems:
- mounted from /etc/fstab (where it uses LABEL=):
[ 149.763638] device label btrfs1 devid 2 transid 7 /dev/sdb5
[ 149.764127] btrfs: force zlib compression
[ 149.764170] btrfs: disk space caching is enabled
[ 149.765271] btrfs: failed to read the system array on sdb5
[ 149.830891] btrfs: open_ctree failed
[ 149.836563] device label btrfs2 devid 1 transid 7 /dev/sdc1
[ 149.837005] btrfs: force zlib compression
[ 149.837050] btrfs: disk space caching is enabled
[ 149.837660] btrfs: failed to read the system array on sdc1
[ 149.910828] btrfs: open_ctree failed
- mounted with /dev/sdc1 only:
[ 173.688956] device label btrfs2 devid 1 transid 7 /dev/sdc1
[ 173.689393] btrfs: disk space caching is enabled
[ 173.690195] btrfs: failed to read the system array on sdc1
[ 173.796816] btrfs: open_ctree failed
Is it expected behaviour that the fs is mountable only once?
--
Tomasz Chmielewski
http://www.ptraveler.com
next reply other threads:[~2013-06-12 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 11:53 Tomasz Chmielewski [this message]
2013-06-13 7:42 ` can't mount a newly created fs after reboot Duncan
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=20130612205303.308095ca@virtall.com \
--to=tch@virtall.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.