As you were in the process of a rebalance these errors may actually be caused by this serious bug "Btrfs: relocate csums properly with prealloc extents".
I hit that myself with several preallocated files made by rtorrent during a rebalance and I lost several huge files as a consequence. The only way I could rebalance without large scale corruptions was to manually patch the 3.11.6 kernel with the small patch that fixes the issue. For some reason this patch is not pushed upstream yet. I think that is strange as it leads to corruption and actual data loss and it is 100% reproducible with preallocated files. Only systemd logs is mentioned in the bug reports, but in my case it was actually hitting several terabytes of files created by rtorrent. Mvh Hans-Kristian Bakke On 5 November 2013 02:24, Russell Coker <russ...@coker.com.au> wrote: > 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 majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
