From: Michael Conrad <mconrad-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Bug? Kernel doesn't prevent multiple rw nilfs mounts
Date: Thu, 24 Oct 2013 13:21:08 -0400 [thread overview]
Message-ID: <52695704.3010507@intellitree.com> (raw)
Hi, When I mount a NILFS partition twice (not on purpose), it correctly
prints:
mount.nilfs2: the device already has a rw-mount on /mnt/_bak.
multiple rw-mount is not allowed.
But the mount happens anyway?!
/dev/sdb4 on /mnt/_bak type nilfs2 (rw,relatime)
/dev/sdb4 on /mnt/sdb4 type nilfs2 (rw,relatime)
I saw this in Linux 3.2.16, then upgraded to 3.10.7 and it still
happens. Writing to these mounts in parallel causes buggy behavior,
though it didn't corrupt my partition (yet).
Has no-one tested this lately?
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-10-24 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 17:21 Michael Conrad [this message]
[not found] ` <52695704.3010507-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
2013-10-24 18:07 ` Bug? Kernel doesn't prevent multiple rw nilfs mounts Vyacheslav Dubeyko
[not found] ` <76524A8B-8063-4335-9B26-615417123CDE-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-10-24 19:05 ` Michael Conrad
[not found] ` <52696F86.70203-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
2013-10-24 19:57 ` Vyacheslav Dubeyko
[not found] ` <B40AD6B8-5EB1-4F64-9224-2F684AE3DF8A-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2013-10-24 20:01 ` Michael Conrad
[not found] ` <52697C8B.3090407-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
2013-10-25 1:38 ` Ryusuke Konishi
[not found] ` <20131025.103819.27810920.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-10-25 1:54 ` Ryusuke Konishi
2013-10-25 16:26 ` Michael Conrad
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=52695704.3010507@intellitree.com \
--to=mconrad-hsdw+lvsy7tz66hez9pjww@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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