The below messages are from dmesg on a system where "btrfs balance" just aborted. It's running kernel 3.11.6 (the latest Debian package). This seems to be telling me that Inode 388 is involved, but there are over 300 subvols on that system which could contain such an Inode. I think that more information is needed for such log messages. We need to at least be able to identify the subvol (is it possible to extract this from the numbers in the log messages?). Ideally we would be able to identify the file name as well. [10751.637517] BTRFS info (device sda3): csum failed ino 388 off 23191552 csum 2566472073 private 3193692311 [10751.646390] BTRFS info (device sda3): csum failed ino 388 off 24104960 csum 5219137 private 2264608335 [10751.654472] BTRFS info (device sda3): csum failed ino 388 off 24154112 csum 4084831521 private 1792217768 [10751.731830] BTRFS info (device sda3): csum failed ino 388 off 23191552 csum 2566472073 private 3193692311 -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
