FSCK failed does'nt correct file size when INCORRECT BLOCK COUNT is found

[Jim Rees]

Dag-Erling Smørgrav wrote:

  Get a UPS.

We should strive to prevent data corruption in the face of unexpected system
shutdown.  Having a user who loses power several times a week seems useful
for testing, especially when he is willing to delve into fsck sources and
figure out what's going on.  My recommendation would be to turn off caching
in the disk and report back in a couple of weeks.