From: Michael Conrad <mconrad-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Bug? Kernel doesn't prevent multiple rw nilfs mounts
Date: Thu, 24 Oct 2013 16:01:15 -0400 [thread overview]
Message-ID: <52697C8B.3090407@intellitree.com> (raw)
In-Reply-To: <B40AD6B8-5EB1-4F64-9224-2F684AE3DF8A-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
On 10/24/2013 3:57 PM, Vyacheslav Dubeyko wrote:
> What do you mean when you are talking about two systems?
> Do you have two systems are working in parallel with one NILFS2 partition?
> What is your configuration?
Separate systems. Each has 2 SATA disks (a main drive, and a second for
backups). These are test/development servers I use, and running regular
consumer hardware. I added a second drive to each just to experiment
with NILFS. (BTW, I had problems when running NILFS on a loopback
device on System 1. I can investigate that further later.)
I tried NILFS on System 1 a few days ago, and ran into the problem. I
decided to try a newer kernel, but tried from scratch on System 2
instead of upgrading System 1. The only thing they have in common is
that they are gentoo-based and 32-bit. They have very different
hardware and very different kernel configs.
The double-mount should be prevented at the kernel level, right? I
could try a linux version direct from kernel.org, next.
If the double-mount should be prevented in user-space, then I could
check things like the libc, compiler, strace, etc.
Which would you like next?
-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 prev parent reply other threads:[~2013-10-24 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 17:21 Bug? Kernel doesn't prevent multiple rw nilfs mounts Michael Conrad
[not found] ` <52695704.3010507-HsDW+lVSy7tZ66HEZ9PjWw@public.gmane.org>
2013-10-24 18:07 ` 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 [this message]
[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=52697C8B.3090407@intellitree.com \
--to=mconrad-hsdw+lvsy7tz66hez9pjww@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=slava-yeENwD64cLxBDgjK7y7TUQ@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 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.