From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot
Date: Fri, 1 Apr 2011 23:24:12 GMT [thread overview]
Message-ID: <201104012324.p31NOChK001774@demeter2.kernel.org> (raw)
In-Reply-To: <bug-32482-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=32482
Eric Sandeen <sandeen@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandeen@redhat.com
--- Comment #5 from Eric Sandeen <sandeen@redhat.com> 2011-04-01 23:24:10 ---
ext4 now has the helpful feature of reminding you about errors it encountered
in the past, and doing so on a regular basis.
Isn't that a helpful message? ;) I think it gets truncated.
I think it came out of:
584 if (ext4_check_dir_entry(dir, NULL, de, bh,
585 (block<<EXT4_BLOCK_SIZE_BITS(dir->i_sb))
586 + ((char *)de - bh->b_data))) {
have you tried running e2fsck -f on the filesystem? Looks like you have a
problem in a directory.
-Eric
--
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:[~2011-04-01 23:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 21:29 [Bug 32482] New: "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot bugzilla-daemon
2011-04-01 21:30 ` [Bug 32482] " bugzilla-daemon
2011-04-01 21:31 ` bugzilla-daemon
2011-04-01 21:32 ` bugzilla-daemon
2011-04-01 21:34 ` bugzilla-daemon
2011-04-01 21:50 ` bugzilla-daemon
2011-04-01 23:24 ` bugzilla-daemon [this message]
2011-04-02 7:58 ` bugzilla-daemon
2011-04-03 3:01 ` Ted Ts'o
2011-04-02 8:09 ` bugzilla-daemon
2011-04-03 3:43 ` bugzilla-daemon
2011-04-03 9:48 ` bugzilla-daemon
2011-04-04 14:14 ` 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=201104012324.p31NOChK001774@demeter2.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).