linux-ext4 - [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: <201104012324.p31NOChK001774@demeter2.kernel.org>
Date:	Fri, 1 Apr 2011 23:24:12 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block
 1056737" message after every boot

https://bugzilla.kernel.org/show_bug.cgi?id=32482


Eric Sandeen <sandeen@...hat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@...hat.com




--- Comment #5 from Eric Sandeen <sandeen@...hat.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.
--
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