From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 93031] New: root becomes read-only at boot due to journal_async_commit in /etc/fstab
Date: Tue, 10 Feb 2015 07:59:55 +0000 [thread overview]
Message-ID: <bug-93031-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=93031
Bug ID: 93031
Summary: root becomes read-only at boot due to
journal_async_commit in /etc/fstab
Product: File System
Version: 2.5
Kernel Version: 3.18.5
Hardware: x86-64
OS: Linux
Tree: Fedora
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: mtall.qld@gmail.com
Regression: No
Booting kernel 3.18.5 with the journal_async_commit option for / in /etc/fstab
causes the root file system to be read-only. kernel 3.18.3 also has this
problem.
entry in /etc/fstab:
UUID=... / ext4 defaults,nodiratime,noatime,journal_async_commit 1 1
Relevant log from dmesg:
EXT4-fs (sdb1): changing journal_checksum during remount not supported
Adding journal_checksum to /etc/fstab doesn't help. Trying to manually remount
root to enable or disable journal_async_commit also doesn't work.
kernel 3.17.x works without problems.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-02-10 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 7:59 bugzilla-daemon [this message]
2015-02-10 8:00 ` [Bug 93031] root becomes read-only at boot due to journal_async_commit in /etc/fstab bugzilla-daemon
2015-02-10 16:53 ` bugzilla-daemon
2015-08-18 10:55 ` bugzilla-daemon
2015-10-22 22:06 ` bugzilla-daemon
2015-10-23 12:27 ` bugzilla-daemon
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=bug-93031-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).