Hi there, your report was "Filesystem on a USB disk, journaling disabled, mounted read-write. rdiff-backup was trying to clean up after a previously aborted backup. The file system is now broken, Mac OS' Disk Utility failed to repair the file system. It reported an "invalid sibling link", then tried "rebuilding catalog B-tree" unsuccessfully." Just so that I fully understand the cause of the problem:
1. Did the running of rdiff-backup trigger the reported Oops and cause the broken filesystem? 2. Or was the oops caused later when you tried to do rdiff-backup on an already broken filesytem? I've looked at the oops and disassembled the code. Essentially what is happening is the the deleted file or directory causes a tree to be rebalanced and the parent needs to be expanded. The "hfs: splitting index node..." message indicates that a node is too big and is split into more nodes. I believe the Oops occurs when the parent node is being updated. A few more questions: Is the filesystem salvageable with fsck? Can you re-trigger this kernel Oops message? I've tried to reproduce this bug, but as yet, not succeed. Any information on the kind of structure of the tree may be helpful (e.g. depth of directory tree, etc..) to try and help me reproduce this. Many thanks. Colin -- hfsplus oops, corrupted file system https://bugs.launchpad.net/bugs/202595 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
