https://bugzilla.kernel.org/show_bug.cgi?id=219132 Theodore Tso (tytso@xxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tytso@xxxxxxx --- Comment #2 from Theodore Tso (tytso@xxxxxxx) --- The suggestion in #1 isn't necessarily correct, though, because we could be remounting to change some other superblock options. For example: mount -o remount,errors=continue /dev/vdc Fundamentally, whenever runs "mount -o remount ...", we issue the "EXT4-fs (DEVICE): re-mounted ..." message. The fact that we print the ro/rw and quota mode is completely arbitrary and more due to historical reasons than anything else. For example, the fact that we print the quota mode is pretty much useless in this day and era and there are plenty of other mount option/state that would probably be much more useful. So the fact that we print the ro/rw state doesn't imply that it has changed. For example, if the file system is mounted read/write and we change the errors= mode from continue to remount-ro, etc., we will print: EXT4-fs (nvme0n1p3): re-mounted UUID rw. Quota mode: none. ... and it doesn't mean that we changed the rw/ro mode from ro to r/w. Should we change the behavior to something else? Perhaps, although to be honest it's not the highest priority thing for me. I could see dropping the quota mode and only printing the message when the r/o state changes. Or maybe we display any mount option that changes (which would be a lot more work). Is it worth the effort? Meh..... . -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
