#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:12 umccullough]: > Replying to [comment:10 axeld]: > > You didn't need to redo the test, or are you doing so with a clean image every time? > > Yep, it is so repeatable for me (pretty much 100% with the scenario I have outlined), I wasn't that worried about losing it, so I just create a new test image for each subsequent test. > > FWIW, I am also able to create a last_modified b+tree issue pretty consistently with this: > > {{{ > ~> cp -a /boot/common . > }}} > > And even once when I ran that, I got an ASSERTION FAILED panic in vfs.cpp which appears to be #3159 > > I'll keep trying to reproduce that particular failure as well, since it seems pretty important. Try unzipping something with allot of folders to the disk with the bfs error. Thats seems to do the trick for reproducing that vfs issue. Works for me at least. Expander and unzip do a handy job of triggering that issue. See it all the time when the build completes and starts making the image. -- Ticket URL: <http://dev.haiku-os.org/ticket/8408#comment:15> Haiku <http://dev.haiku-os.org> Haiku - the operating system.