#6170: BFS panic on certain files ------------------------------+--------------------------------------------- Reporter: Ziusudra | Owner: axeld Type: bug | Status: new Priority: critical | Milestone: R1 Component: File Systems/BFS | Version: R1/Development Keywords: | Blockedby: Patch: 0 | Platform: All Blocking: | ------------------------------+--------------------------------------------- Changes (by axeld): * priority: normal => critical Comment: Looks like your directory's B+tree was corrupted. Unfortunately, it's usually hard to know whose fault that is after the fact; you can just see that BFS gracefully handles the case - it just panics because that's what it should do for now ;-) It would be interesting to see what kind of data made it into the B+tree. You can use 'ls -i' to find out which inode number the parent directory has, and then use bfsinfo part of BFS tools, available on BeBits) to have a look at their contents. Hopefully, the B+tee is just broken in a harmless way (ie. no foreign data), and that would point to a bug in the B+tree implementation, which would then hopefully be a duplicate or related to bug #6034. -- Ticket URL: <http://dev.haiku-os.org/ticket/6170#comment:1> Haiku <http://dev.haiku-os.org> Haiku - the operating system.