From: "Misono, Tomohiro" <misono.tomohiro@jp.fujitsu.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: bug report: mounting the same device to different mount points in parallel may fail
Date: Thu, 18 Jan 2018 13:23:35 +0900 [thread overview]
Message-ID: <db01b798-cc0a-f276-df4d-e9c334ea912e@jp.fujitsu.com> (raw)
Although I think this rarely happens in the real world, mounting
the same device to different mount points in parallel may fail:
- kernel 4.15.0-rc8
- Procedure
[mount.sh]
#!/bin/bash
for i in `seq 1 1000`; do
echo $i
mount $1 $2
umount $2
if [ $? -ne 0 ]; then
exit 1;
fi
done
$ mkfs.btrfs -f /dev/sde
$ ./mount.sh /dev/sde /mnt
$ ./mount.sh /dev/sde /mnt2 (on the different terminal)
- stdout
mount: /mnt2: wrong fs type, bad option, bad superblock on
/dev/sde, missing codepage or helper program, or other error.
- dmesg
[ 108.122576] BTRFS error (device sde): super_total_bytes 199481098240 mismatch with fs_devices total_rw_bytes 398962196480
[ 108.122647] BTRFS error (device sde): failed to read chunk tree: -22
[ 108.150060] BTRFS error (device sde): open_ctree failed
xfs or ext4 works fine.
Regards,
Tomohiro Misono
reply other threads:[~2018-01-18 4:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=db01b798-cc0a-f276-df4d-e9c334ea912e@jp.fujitsu.com \
--to=misono.tomohiro@jp.fujitsu.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 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).