Invalid b+tree after installing
|Reported by:||humdinger||Owned by:||axeld|
This is hrev43873 gcc2hybrid.
Checkfs is revealing "invalid b+tree" failures. Even a completely new installation has them. I put a new nightly on the stick and used Installer to put it all on freshly initialized partition. Checkfs says:
size (inode = 4296), invalid b+tree
In the syslog appears:
KERN: inode 4296: duplicate at 318464 has invalid array size 0! KERN: inode 4296: visited 415 from 416 nodes.
I then initialized the partition again and copied one folder at a time from the USB stick onto it. Now checkfs showed no invalid b+trees. I redid that copying all folders at once via Tracker and still no invalids. Redid the Installer way, and got the same invalid b+tree.
My /boot drive BTW now has:
last_modified (inode = 4261), invalid b+tree name (inode = 4195), invalid b+tree
I attach the rather longer syslog for that checkfs run with "checkfs-boot-syslog.txt".
My "Generator" partition, where I put the "generated" folders for building Haiku, does one better and says:
last_modified (inode = 4424), invalid b+tree name (inode = 4358), invalid b+tree size (inode = 4457), invalid b+tree
I attach the even longer syslog for that checkfs run with "checkfs-Generator-syslog.txt".
The Generator might be corrupted from KDLs I currently experience every time I try to build Haiku.
BTW, I have other partitions that don't show invalid b+trees (yet?).
I'm just putting this ticket out there in case sombody sees a pattern here...