Skip to contentSkip to conversation

New: fs/jbd2/transaction.c:1113 and fs/buffer.c:2915

Bug 41962 [email protected] 2 participants 2 messages Jun 25, 2014 – Aug 2, 2022

lore
Share & tools
lore
#0 lore raw

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

            Bug ID: 41962
           Summary: fs/jbd2/transaction.c:1113 and fs/buffer.c:2915
           Product: File System
           Version: 2.5
    Kernel Version: 3.0.3
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
        Regression: No
                CC: [email protected]

Created attachment 70802
--> https://bugzilla.kernel.org/attachment.cgi?id=70802&action=edit
dmesg

Certain filesystem usage leads to one of the two errors visible in dmesg output (see attachment). The system needs a reboot after that.

I have also tested with olders kernel versions, including 2.6.38.8. Same there (at least for the first of the two errors).

Strangely, the only filesystem usage scheme that triggers those errors are two parallel processes of the bup backup system <https://github.com/apenwarr/bup>.
They run fine for some time (several minutes, sometimes longer), then the bug message appears in the logs, and the system stops working correctly.

I am using an encrypted LVM.

--- Comment #1 from [email protected] ---
Please test this bug against a newer kernel to see if it's fixed. Cheers Nick

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
#1 lore raw

[Bug 41962] fs/jbd2/transaction.c:1113 and fs/buffer.c:2915

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

Artem S. Tashkinov ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |OBSOLETE
Signature · 4 lines
You may reply to this email to add a comment.

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