Red Hat Bugzilla – Bug 998121
4 repeating errors at every fsck: HTREE directory inode <number> has a tree depth (0) which is too big
Last modified: 2014-04-15 11:53:40 EDT
Created attachment 787550 [details]
vmware boot screenshot
this sounds like https://bugzilla.redhat.com/show_bug.cgi?id=557959 but a completly different issue *everytime* the system is booted with a forced fsck
translation to english:
HTREE directory Inode <number> has a too large directory depth about (0)
hence, how can (0) zero bee too large and if it has been cleared why does it appear at every reboot? :-)
Hm the real message is this in english:
"HTREE directory inode %i has a tree depth (%N) which is too big"
Would you be willing to provide an e2image (possibly off-line?) - that would aid analysis since it's the reproducer...
since it is a virtual machine and folder-depth seems to be the problem i try to delete all *files*, fill the space with zeros and look if fsck insists to complain - if so a tar.xz of the vmware-vmdk should even fit as attachment to the bugreport :-)
argh - the problem diesappeared at all, maybe caused by a crash yesterday and the resulting repair did really change anything instead only saying it does :-(
i keep this bugreport and the hint about e2image bookmarked if it comes back
Ok, without the reproducer I don't see a good way to proceed. If it does come back please feel free to re-open.