From: Ted Ts'o <tytso@mit.edu>
To: egokillsall@gmail.com, bugzilla-daemon@bugzilla.kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: Re: [Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot
Date: Sat, 2 Apr 2011 23:01:04 -0400 [thread overview]
Message-ID: <20110403030104.GA20349@thunk.org> (raw)
In-Reply-To: <201104020758.p327wAMh010746@demeter1.kernel.org>
This message will get reset if you use the e2fsck from e2fsprogs
1.41.13 or later. I recommend using e2fsprogs 1.41.14.
You can translate the "initial error" and "last error" time stamps in
the kernel messages here:
kernel: EXT4-fs (sda10): error count: 5
kernel: EXT4-fs (sda10): initial error at 1301325048: htree_dirblock_to_tree:586: inode 260099: block 1056737
kernel: EXT4-fs (sda10): last error at 1301325083: htree_dirblock_to_tree:586:
inode 260099: block 1056737
via the date command:
% date --date=@1301325048
Mon Mar 28 11:10:48 EDT 2011
% date --date=@1301325083
Mon Mar 28 11:11:23 EDT 2011
(We use seconds since the epoch because we don't want to put time zone
conversion routines in the kernel.)
In any case, it's not a big deal, and you can fix this easily by
upgrading to a newer version of e2fsprogs.
- Ted
next prev parent reply other threads:[~2011-04-03 3:01 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
2011-04-02 7:58 ` bugzilla-daemon
2011-04-03 3:01 ` Ted Ts'o [this message]
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=20110403030104.GA20349@thunk.org \
--to=tytso@mit.edu \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=egokillsall@gmail.com \
--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).