Re: corrupt node with extent csum item results in bogus data being read

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I realized this could be a much bigger problem for single copy
metadata on SSD case, rather than the example using raid1 where it's
unlikely for both copies of the node to be corrupt. So I filed a bug.

https://bugzilla.kernel.org/show_bug.cgi?id=118321
--
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




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux