From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219132] New: Redundant "re-mounted ro" message
Date: Tue, 06 Aug 2024 18:20:06 +0000 [thread overview]
Message-ID: <bug-219132-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219132
Bug ID: 219132
Summary: Redundant "re-mounted ro" message
Product: File System
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: low
Priority: P3
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: aros@gmx.com
Regression: No
I'm not a fan of ext4 logging this:
EXT4-fs (nvme0n1p3): re-mounted UUID ro. Quota mode: none.
when the filesystem was already mounted RO.
It's confusing and may lead the user to believe the FS was mounted RW
previously.
I'd like the ext4 driver to ignore or not log RO remount requests when the FS
is already mounted RO.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-08-06 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 18:20 bugzilla-daemon [this message]
2024-08-06 19:14 ` [Bug 219132] Redundant "re-mounted ro" message bugzilla-daemon
2024-08-07 3:33 ` bugzilla-daemon
2024-08-07 9:53 ` bugzilla-daemon
2024-08-07 13:41 ` 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-219132-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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