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: Mon, 13 Aug 2012 19:34:25 +0000 (UTC) [thread overview]
Message-ID: <20120813193425.7199511FB49@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-16583-13602@https.bugzilla.kernel.org/>
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.
next prev parent reply other threads:[~2012-08-13 19:34 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 ` [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 [this message]
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=20120813193425.7199511FB49@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).