From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 41962] New: fs/jbd2/transaction.c:1113 and fs/buffer.c:2915
Date: Wed, 25 Jun 2014 16:11:27 +0000 [thread overview]
Message-ID: <bug-41962-13602@https.bugzilla.kernel.org/> (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: fs_ext4@kernel-bugs.osdl.org
Reporter: lasse-kernel-bug-2011@mail.plastictree.net
CC: xerofoify@gmail.com
Regression: No
CC: xerofoify@gmail.com
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 xerofoify@gmail.com ---
Please test this bug against a newer kernel to see if it's fixed.
Cheers Nick
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-06-25 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 16:11 bugzilla-daemon [this message]
2022-08-02 13:23 ` [Bug 41962] fs/jbd2/transaction.c:1113 and fs/buffer.c:2915 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-41962-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