On Mon, 30 Jun 2014 20:47:28 Noah O'Donoghue wrote: > On 30 June 2014 20:27, Russell Coker <[email protected]> wrote: > > Another thing you should consider is the possibility of bitrot inside your > > PC. > > A while ago I had a damaged DIMM in my PC and it corrupted the BTRFS > > filesystem > > twice before I realised the cause. > > Wouldn't this still cause detectable bitrot though? If the ram somehow > corrupts data being written to disk, it's not going to be able to write a > checksum that matches, so something is going to fail at the next read?
It is possible to have a data block corrupted just before the checksum is calculated, that wouldn't register as a filesystem error. In the cases I know of the filesystem metadata blocks didn't match each other and the kernel paniced. I copied all the data off the filesystem both times but I have no way of ever knowing if some data was corrupted first. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
