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

[julien]

I can't get a UPS in my environment.

I already tested with the write cache desactivated, but the problem 
still the same, I obtain files with holes and incorrect size and 
blockcount. The only difference is that there is less holes and 
performance are falling down.

The problem is really easy to reproduce, you have just to copy several 
big files and shutdown the power in the midle of the copy.




Jim Rees a écrit :
> 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.
>
>
>