Once in a while I get a "DANGER! Wrong file CRC" error on a random content.tmp file. Instead of aborting the process, could SnapRAID instead try re-writing the content and continue if successful?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is that a snapraid content file? If yes that's the sign of a much bigger issue that should be investigated ASAP - is the disk failing (badly, as it can't hold reliably a file which probably is just a fraction of a gigabyte), is there some other snapraid process ignoring the lock, is the RAM failing, is there a snapraid bug, etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am aware of that, however the system is stable under all memory tests, and the hard drives are routinely and thoroughly tested. The issue is intermittent and likely due to minor instability while SnapRAID is writing (or CRC checking) all 28 content files simultaneously. I have one content file on each drive. Since SnapRAID always requires multiple content files, a CRC error in just one of them should not be a fatal error.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Once in a while I get a "DANGER! Wrong file CRC" error on a random content.tmp file. Instead of aborting the process, could SnapRAID instead try re-writing the content and continue if successful?
Is that a snapraid content file? If yes that's the sign of a much bigger issue that should be investigated ASAP - is the disk failing (badly, as it can't hold reliably a file which probably is just a fraction of a gigabyte), is there some other snapraid process ignoring the lock, is the RAM failing, is there a snapraid bug, etc.
Hi Quaraxkad,
John is right. This seems the effect of a more serious problem.
It's better if you check your memory with: http://www.memtest86.com/
Ciao,
Andrea
I am aware of that, however the system is stable under all memory tests, and the hard drives are routinely and thoroughly tested. The issue is intermittent and likely due to minor instability while SnapRAID is writing (or CRC checking) all 28 content files simultaneously. I have one content file on each drive. Since SnapRAID always requires multiple content files, a CRC error in just one of them should not be a fatal error.