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  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]
Date:	Sat, 2 Apr 2011 07:58:10 GMT
Subject: [Bug 32482] "htree_dirblock_to_tree:586: inode 260099: block
 1056737" message after every boot

--- Comment #6 from Tom <>  2011-04-02 07:58:08 ---
Thanks for your input Eric; yes, fsck is happy all the time (also with -fcc
flags). Find -xdev -inum 260099 shows nothing either, but in the past there was
possibly something there, so it makes sense regarding 'past stuff reminder'.
Anyway it would be *a bit more helpful* if it would tell us something about
it's *cool* behaviour, or at least some hint about some action I'd be able to
pop to clean things up.
De ja vu in the aspect of SMART, because n-2 of my n drives suffer from lovely
errors like 'uncorrectable' (because of bad cabling what got solved of course)
and 'write_dma' (right after I pulled the laptop out of the factory sealed box)
and such.
However this drive is one out of the ones without any error, and the long
self-test ran on it shows zero faults.
Memtest also passes all the time. At night.

Anything I can do to 'reset' this thing, or maybe some other recommendation I
should give a go?

Configure bugmail:
------- 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
More majordomo info at

Powered by blists - more mailing lists