Troubleshooting cache data corruption
This goes back a few years, but it's a condition
that is always possible. The symptoms were occasional
data corruption but only in frequently used files. All
the usual suspects were hauled out and examined; network
problems, application bugs, user error, hard disk sectors:
everything passed muster.
I was called in, and after listening to the sad tale,
I wrote a little shell script very similar to this:
cd /yourdatadir # change this to wherever your files are
echo "Flushing cache"
ls -lR /
sum * > /tmp/firstread
sum * > /tmp/a
sum * > /tmp/b
diff /tmp/a /tmp/b || break
echo "Corruption detected!"
echo "a vs. firstread"
diff /tmp/a /tmp/firstread
echo "b vs. firstread"
diff /tmp/b /tmp/firstread
echo "Flushing cache"
ls -lR /
sum * > /tmp/newread
echo "firstread vs. newread:"
diff /tmp/firstread /tmp/newread
The idea here is that data read from the disk should
always have the same sum (assuming a quiescent system). The
data files were small enough that all data read would be
cached, and the only thing that each "sum" would do
after the first is read from cache. Therefor, if there
was any change in the sums, cache would be the problem.
Indeed, after twenty minutes or so, the script exited,
announcing a difference.
As there was no difference betwwen "firstread" and "newread",
nothing had changed on the disk itself (unless it coincidentally
switched back; rather unlikely): cache definitely was looking very
guilty. But which cache? Was it the system buffer cache or the
raid controller? To determine that, I disabled the disk cache
(fortunately easy to do with that controller). The test was
repeated, and no errors were observed after an hour. I then
re-enabled the disk cache, and was able to repeat the
sum errors within a few minutes. That seemed to be pretty
definite proof of where the problem was, so the hardware was
replaced the following week and, as expected, the corruption
If this page was useful to you, please help others find it:
More Articles by Tony Lawrence
- Find me on Google+
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site:
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Publishing your articles here
Jump to Comments
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.