On Wed, Jan 09, 2013 at 02:59:25PM -0200, Renato Zannon wrote: > From my very limited knowledge, that's all the relevant information I > have. If there's anything else I can do I would be glad to help.
Thanks for the report. > [ 3850.907905] kernel BUG at fs/btrfs/inode.c:881! cow_file_range: 880 BUG_ON(disk_num_bytes > 881 btrfs_super_total_bytes(root->fs_info->super_copy)); The point of crash has been seen some time ago, and I was not able to find any other than my own post http://permalink.gmane.org/gmane.comp.file-systems.btrfs/16227 It was possible to trigger the crash if the filesystem was created with a bigger size than the blockdevice (-b check), but as we've talked on IRC, this was not your case. I'm out of ideas how this could normally happen. For a single device the filesystem size accounted by superblock and by sum of all block groups should the same given that no devices are added/removed. david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
