linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Bug 16583] New: ext4: delayed block allocation failed and application not respond any more
@ 2010-08-13 20:01 bugzilla-daemon
  2012-05-24 13:13 ` [Bug 16583] " bugzilla-daemon
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: bugzilla-daemon @ 2010-08-13 20:01 UTC (permalink / raw)
  To: linux-ext4

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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug 16583] ext4: delayed block allocation failed and application not respond any more
  2010-08-13 20:01 [Bug 16583] New: ext4: delayed block allocation failed and application not respond any more bugzilla-daemon
@ 2012-05-24 13:13 ` bugzilla-daemon
  2012-08-13 15:48 ` bugzilla-daemon
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2012-05-24 13:13 UTC (permalink / raw)
  To: linux-ext4

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


Loredan Stancu <salecss@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |salecss@gmail.com




--- Comment #1 from Loredan Stancu <salecss@gmail.com>  2012-05-24 13:13:00 ---
Hi guys,

Any new on this? I just had the same problem with the ext4 file system after
resizing it from a LVM.

I'm using RHEL 6.3, kernel 2.6.32-262.el6.x86_64.

What I did was to:

1. Umount the LVM partion
2. check it with fsck.ext4 tool (no errors reported)
3. resize the file system using resize2fs tool (no errors reported)
4. resize the LVM using lvresize tool (no error reported)
5. run fsck.ext4 for the resulted file system and no errors was reported.

I was able to mount the new file system but when trying to use db2 database
from that partition I received the following file system error and db2 instance
crashed suddenly:

EXT4-fs error (device dm-2): ext4_ext_search_left: inode #716: (comm db2sysc)
ix (3714852) != EXT_FIRST_INDEX

A fix for me was to create a new LVM and rsync all the files from bad
filesystem to the new one. And worked perfectly. A hadn't any problem to access
the files from the bad file system.

I this a well known problem? 

Regards,
Loredan

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug 16583] ext4: delayed block allocation failed and application not respond any more
  2010-08-13 20:01 [Bug 16583] New: ext4: delayed block allocation failed and application not respond any more bugzilla-daemon
  2012-05-24 13:13 ` [Bug 16583] " bugzilla-daemon
@ 2012-08-13 15:48 ` bugzilla-daemon
  2012-08-13 15:49 ` bugzilla-daemon
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2012-08-13 15:48 UTC (permalink / raw)
  To: linux-ext4

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


Alan <alan@lxorguk.ukuu.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alan@lxorguk.ukuu.org.uk




--- Comment #2 from Alan <alan@lxorguk.ukuu.org.uk>  2012-08-13 15:48:55 ---
RHEL kernel bugs should be reported to Red Hat, the RHEL kernel differs
siginficantly from upstream

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug 16583] ext4: delayed block allocation failed and application not respond any more
  2010-08-13 20:01 [Bug 16583] New: ext4: delayed block allocation failed and application not respond any more bugzilla-daemon
  2012-05-24 13:13 ` [Bug 16583] " 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
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2012-08-13 15:49 UTC (permalink / raw)
  To: linux-ext4

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


Alan <alan@lxorguk.ukuu.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |OBSOLETE




-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug 16583] ext4: delayed block allocation failed and application not respond any more
  2010-08-13 20:01 [Bug 16583] New: ext4: delayed block allocation failed and application not respond any more bugzilla-daemon
                   ` (2 preceding siblings ...)
  2012-08-13 15:49 ` bugzilla-daemon
@ 2012-08-13 19:34 ` bugzilla-daemon
  2012-08-14  7:35 ` bugzilla-daemon
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2012-08-13 19:34 UTC (permalink / raw)
  To: linux-ext4

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


Theodore Tso <tytso@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@mit.edu




--- Comment #3 from Theodore Tso <tytso@mit.edu>  2012-08-13 19:34:25 ---
Also, in the original bug report, (which was against an usptream kernel,
2.6.35) note:

EXT4-fs (dm-6): warning: mounting fs with errors, running e2fsck is recommended

If this means the file system was mounted with inconsistencies noted in the
past.

And sure enough...

EXT4-fs error (device dm-6): ext4_ext_search_left: inode #3510: (comm
flush-254:6) ix (42117) != EXT_FIRST_INDEX (0) (depth 1)!

... is a file system inconsistency. 

The second reporter, Loredan, was using a Red Hat modified 2.6.32 kernel, and
the RHEL 2.6.32 kernel is significantly different from upstream.  I will note
that it wasn't clear whether the file system was being grown or shrunk, but in
the more typical case of growing the file system, in general you should resize
the LVM first, and *then* run resize2fs to resize the filesystem to use the
newly enlarged LV.

Regards,

-- Ted

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug 16583] ext4: delayed block allocation failed and application not respond any more
  2010-08-13 20:01 [Bug 16583] New: ext4: delayed block allocation failed and application not respond any more bugzilla-daemon
                   ` (3 preceding siblings ...)
  2012-08-13 19:34 ` bugzilla-daemon
@ 2012-08-14  7:35 ` bugzilla-daemon
  4 siblings, 0 replies; 6+ messages in thread
From: bugzilla-daemon @ 2012-08-14  7:35 UTC (permalink / raw)
  To: linux-ext4

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





--- Comment #4 from Loredan Stancu <salecss@gmail.com>  2012-08-14 07:35:39 ---
Hi Ted,

Thank you for your reply.


What I wanted to do was to shrunk the files system. This is why first I run
resize2fs (after unmounting and checking the file system with fsck.ext4).

Best Regards,
Loredan

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2012-08-14  7:35 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-08-13 20:01 [Bug 16583] New: ext4: delayed block allocation failed and application not respond any more bugzilla-daemon
2012-05-24 13:13 ` [Bug 16583] " 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

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).