Opened 9 years ago

Closed 2 years ago

#6170 closed bug (invalid)

BFS panic on certain files

Reported by: Ziusudra Owned by: axeld
Priority: critical Milestone: R1
Component: File Systems/BFS Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All


I have certain files that cause BFS to panic when deleting, copying or moving them with Tracker. checkfs and rm also trigger the panic. Continuing 3 times will allow the action to complete and the fs will be readonly.

I can tar the file or copy it to another BFS partition, but it loses whatever causes the panic.

These are object files from building Haiku and Web+, but those are the only cases where I've created a large number of files.

Attachments (4)

empty-trash-bt.jpg (426.2 KB) - added by Ziusudra 9 years ago.
copy-to-bt.jpg (303.6 KB) - added by Ziusudra 9 years ago.
checkfs-bt.jpg (379.2 KB) - added by Ziusudra 9 years ago.
bfsinfo-session.txt (3.6 KB) - added by Ziusudra 9 years ago.

Download all attachments as: .zip

Change History (9)

Changed 9 years ago by Ziusudra

Attachment: empty-trash-bt.jpg added

Changed 9 years ago by Ziusudra

Attachment: copy-to-bt.jpg added

Changed 9 years ago by Ziusudra

Attachment: checkfs-bt.jpg added

comment:1 Changed 9 years ago by axeld

Priority: normalcritical

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.

Changed 9 years ago by Ziusudra

Attachment: bfsinfo-session.txt added

comment:2 Changed 9 years ago by Ziusudra

I just deleted the 3 .o files without error, but the session file will cause a panic. Though in this case it will copy the file without error.

I forgot to mention that when I got an error copying before, if I continued the copy would succeed and the copy of the file would have the same behaviour.

comment:3 Changed 7 years ago by kallisti5

Resolution: fixed
Status: newclosed

This should be resolved with Axel's recent BFS changes. checkfs also can repair BTree's now.

If anyone still encounters this issue post hrev43930, please let us know so we can re-open this bug.

comment:4 Changed 7 years ago by axeld

Resolution: fixed
Status: closedreopened

comment:5 Changed 2 years ago by axeld

Resolution: invalid
Status: reopenedclosed

The bfsinfo output looks completely normal, and doesn't hint to any problem. It doesn't seem to be related to the problematic files mentioned before, though. In any case, this ticket does not hold enough information to do anything about it. There might be a chance that the problem has already been fixed in the mean time, too. If something like this occurs again, please report it again, though.

Note: See TracTickets for help on using tickets.