When I cksum large files (150MB) they will often report different checksums on each call.
$ cksum test3 1233504235 170213376 test3 $ cksum test3 825031809 170213376 test3 $ cksum test3 189847968 170213376 test3 $ cksum test3 1089532177 170213376 test3
This happens consistently in /dev/shm but I've seen it in disk based ext3 filesystems as well.
I am confident the files are not being written to at the time of the checks.
It's been an issue since I upgraded from Debian 6 32bit to 7 32bit but I had similar issues on 64bit Debian 6 (reinstalled 32bit to cure the problem).
The memory has passed multiple Memtest86+ runs. The are no indications of filesystem corruption.
Could there be a BIOS setting; kernel parameter or filesystem flag that I need to set.
filesystem flags are:
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2040740k) /dev/disk/by-uuid/b236be25-6fe1-49f6-83a3-d295643666a4 on / type ext3 (rw,relatime,errors=remount-ro,barrier=1,data=ordered)
This is driving me nuts as my data files keep getting corrupted and I can't use the system.
Booting off the previous kernel (2.6.32) stops the file corruptions. It also reduces the memory from 4GB to 3GB even tho both kernels report 'getconf LONG_BIT' as 32