From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12815] New: JBD: barrier-based sync failed on dm-1:8 - disabling barriers -- and then hang
Date: Tue, 3 Mar 2009 21:08:47 -0800 (PST) [thread overview]
Message-ID: <bug-12815-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=12815
Summary: JBD: barrier-based sync failed on dm-1:8 - disabling
barriers -- and then hang
Product: File System
Version: 2.5
KernelVersion: 2.6.28
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: joey@kitenet.net
Latest working kernel version: none
Earliest failing kernel version: 2.6.28.1
Distribution: Debian unstable
Hardware Environment: Thecus N2100 (arm), two 1 TB SATA drives
Software Environment: /home is an ext4 filesystem on an LVM of the two drives
Problem Description:
This has happened at least three times since I converted the filesystem from
ext3 to ext4 two days ago. All processes accessing the filesystem go into
uninterruptable sleep. The system does not crash. On one occasion, the problem
cleared itself up after a few minutes and processes resumed running. On the
other two, I hard-reset the machine after 8 hours, and half an hour,
respectively.
The only thing in the log is this:
JBD: barrier-based sync failed on dm-1:8 - disabling barriers
It was never logged in the month before switching to ext4, and has been logged
seven times in the past two days. I have not matched up all seven times
exactly with the hangs, but some of them match up very well.
Steps to reproduce:
Unsure, but heavy disk load does not seem to help; at one point rtorrent was
hashing a large file when the hang occurred.
This may be a duplicate of bug 12679 -- at least, the symtoms as described are
the same, and the backtrace obtained there shows a hang in
jbd2_journal_commit_transaction, which calls the function from which my message
originates.
I am running a Debian kernel, not mainline. Apologies, but I don't have a head
on this machine.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-03-04 5:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 5:08 bugme-daemon [this message]
2009-03-04 5:29 ` [Bug 12815] JBD: barrier-based sync failed on dm-1:8 - disabling barriers -- and then hang bugme-daemon
2009-03-04 5:33 ` bugme-daemon
2009-03-04 17:04 ` bugme-daemon
2009-03-04 17:15 ` bugme-daemon
2009-03-04 17:40 ` bugme-daemon
2009-03-07 17:08 ` bugme-daemon
2009-03-09 15:45 ` bugme-daemon
2009-05-19 18:43 ` bugzilla-daemon
2009-08-26 18:08 ` bugzilla-daemon
2010-01-13 21:13 ` bugzilla-daemon
2010-01-13 21:15 ` 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-12815-13602@http.bugzilla.kernel.org/ \
--to=bugme-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;
as well as URLs for NNTP newsgroup(s).