linux-ext4 - Re: [Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block 1056737" message after every boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110403030104.GA20349@thunk.org>
Date:	Sat, 2 Apr 2011 23:01:04 -0400
From:	Ted Ts'o <tytso@....edu>
To:	egokillsall@...il.com, bugzilla-daemon@...zilla.kernel.org
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block
 1056737" message after every boot

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=@...1325048
Mon Mar 28 11:10:48 EDT 2011

% date --date=@...1325083
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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html