From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16583] New: ext4: delayed block allocation failed and application not respond any more
Date: Fri, 13 Aug 2010 20:01:48 GMT [thread overview]
Message-ID: <bug-16583-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=16583
Summary: ext4: delayed block allocation failed and application
not respond any more
Product: File System
Version: 2.5
Kernel Version: 2.6.35.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: andrej.gelenberg@udo.edu
Regression: No
dmesg:
EXT4-fs (dm-6): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (dm-6): recovery complete
EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: acl,commit=100
EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: acl,commit=100
...
EXT4-fs error (device dm-6): ext4_ext_search_left: inode #3510: (comm
flush-254:6) ix (42117) != EXT_FIRST_INDEX (0) (depth 1)!
EXT4-fs (dm-6): delayed block allocation failed for inode 3510 at logical
offset 42117 with max blocks 77 with error -5
This should not happen!! Data will be lost
transmission-daemon (which had the data on dm-6) don't respond anymore and i
can't kill it with kill -9. I can't shutdown the system too (only mit sys-rq
keys).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2010-08-13 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 20:01 bugzilla-daemon [this message]
2012-05-24 13:13 ` [Bug 16583] ext4: delayed block allocation failed and application not respond any more bugzilla-daemon
2012-08-13 15:48 ` bugzilla-daemon
2012-08-13 15:49 ` bugzilla-daemon
2012-08-13 19:34 ` bugzilla-daemon
2012-08-14 7:35 ` 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-16583-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;
as well as URLs for NNTP newsgroup(s).