On Sat, Feb 21, 2009 at 07:48:32AM +1300, Andreas Friedrich Berendsen wrote: > ...I haven't noticed before, but before that message few more lines > where recorded, which makes sense with the BUG line. Also, running > fsck.ext4 on that filesystem I always got a Segment fault at an specific > point, which it is impossible to fix. I'm in a process to remove files > from that filesystem, as soon it finish I can run fsck again and send > the result. Meanwhile, when removing files, rm stuck at a certain inode, > which caused the first BUG message. Have you tried running e2fsck? It sounds like a filesystem corruption is triggering a BUG() message, which is obviously a bug in and of itself. :-) - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
