[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-16583-13602@https.bugzilla.kernel.org/>
Date: Fri, 13 Aug 2010 20:01:48 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 16583] New: ext4: delayed block allocation failed and
application not respond any more
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@...nel-bugs.osdl.org
ReportedBy: andrej.gelenberg@....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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists