From: Calvin Owens <jcalvinowens@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: e2fsprogs: Fsck of read-only FS w/ external journal fails after 1.42.5?
Date: Sat, 4 May 2013 14:53:50 -0500 [thread overview]
Message-ID: <20130504195350.GA20046@gmail.com> (raw)
Hello all,
Commit a85f8350 (http://goo.gl/aCykm) makes it impossible to fsck an
ext4 filesystem w/ external journal if it is mounted read-only. Certain
distros (Gentoo in my case) expect to be able to do this on the root
filesystem at boot time, and get very upset if they can't.
With journal checks forced now, e2fsck tries to open() the external
journal device, which always fails with -EBUSY if the filesystem is
mounted, read-only or otherwise. Is this the expected behavior? Maybe
the kernel shouldn't be returning an error there? It's been doing so
since at least v3.6.
Clearly this doesn't impact many people, since it's been in the tree for
almost a year now... but I thought I'd mention it.
Thoughts?
Thanks very much,
Calvin
next reply other threads:[~2013-05-04 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 19:53 Calvin Owens [this message]
2013-05-04 23:33 ` e2fsprogs: Fsck of read-only FS w/ external journal fails after 1.42.5? Theodore Ts'o
2013-05-05 0:33 ` Calvin Owens
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=20130504195350.GA20046@gmail.com \
--to=jcalvinowens@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).