[Bug 220299] New: Warning Trace seen at https://elixir.bootlin.com/linux/v6.6.69/source/fs/ext4/ext4_jbd2.c#L73 post remount-ro

[Bug 220299] New: Warning Trace seen at https://elixir.bootlin.com/linux/v6.6.69/source/fs/ext4/ext4_jbd2.c#L73 post remount-ro

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=220299

            Bug ID: 220299
           Summary: Warning Trace seen at
                    https://elixir.bootlin.com/linux/v6.6.69/source/fs/ext
                    4/ext4_jbd2.c#L73 post remount-ro
           Product: File System
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: chakrashramana28@gmail.com
        Regression: No

Warning Trace seen at
https://elixir.bootlin.com/linux/v6.6.69/source/fs/ext4/ext4_jbd2.c#L73 is hit
by the writeback system even though there is nothing to write and the
filesystem has been mounted as readonly.

An ext4 fs is mounted with journal=data and a large file is written to it. Then
the fs is mounted as readonly-ro post a sync. At this point of time, data
consistency is preserved through the sync itself followed by a sync from the
remount-ro action. All the dirty pages should be marked as clean in the cache.
Yet post the remount-ro, it hits
https://elixir.bootlin.com/linux/v6.6.69/source/fs/ext4/ext4_jbd2.c#L73 and
prints the trace as the fs is readonly now. Even though there is nothing to
writeback, the wb_writeback is scheduled every 5 secs or so and the same trace
can be seen if changed from WARN_ON_ONCE to WARN_ON.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.