Re: Got 10 csum errors according to dmesg but 0 errors according to dev stats

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

 



On Mon, 11 May 2015 03:32:45 AM Philip Seeger wrote:
> However, it seems strange to me that a bunch of files is corrupted 
> simply because btrfs-progs is older than the kernel.

That won't happen.

> To trigger more csum errors, I ran a script that basically finds all 
> files and runs cat $file >/dev/null. I also scrubbed the filesystem.
> It's getting worse. The number of corrupted files has grown to 79 - all 
> in /home. Some of these files have not been modified in 3 years. I have 

Sounds like you are having errors in your RAM, CPU, motherboard, or hard drive 
cabling.  Turn the machine off ASAP and plug the disks into a different system, 
if you keep it running you will make it worse.

-- 
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




[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