#8408: Invalid b+tree after installing --------------------------------+---------------------------- Reporter: humdinger | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: File Systems/BFS | Version: R1/Development Resolution: | Keywords: invalid b+tree Blocked By: | Blocking: Has a Patch: 0 | Platform: All --------------------------------+---------------------------- Comment (by SeanCollins): Replying to [comment:20 anevilyak]: > > That's more or less completely meaningless since that's precisely the range where B+ tree validation was actually added. hrev43769's checkfs wouldn't report it because it doesn't check for it. I have a 43769, that after 2 weeks of contious use does not have a b+tree error. Thats why I tested this 43769 this morning. I didn't realize the machine I am on right now had the rev, but it does, it also does not show signs of b+tree corruption. Conversly rev 43810 does corrupt within minutes of use. In particular if you unzip lots of directorys or mkdir gets called when downloading the repo from git. There is also a data loss issue that crop up in the same time frame.I can only report the info I have on hand. -- Ticket URL: <http://dev.haiku-os.org/ticket/8408#comment:21> Haiku <http://dev.haiku-os.org> Haiku - the operating system.