From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16583] ext4: delayed block allocation failed and application not respond any more
Date: Thu, 24 May 2012 13:13:00 +0000 (UTC) [thread overview]
Message-ID: <20120524131300.7E58611FD1B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-16583-13602@https.bugzilla.kernel.org/>
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.
next prev parent reply other threads:[~2012-05-24 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2012-08-13 15:48 ` [Bug 16583] " 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=20120524131300.7E58611FD1B@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).