<Eric Sandeen wrote:>
|Sidik Isani wrote:
|> The symptoms are files which were written *minutes* ago retain
|> the right size, but seem to develop blocks full of zero bytes.
|> I think this mostly happens when memory runs very low, but I'm
|> not sure.
|I assume you see this after a crash? Or is this on a live system?
Actually a live system! Often one with no other sign that things
have gone wrong other than files developing zeroed-blocks. Sometimes
a running program will suddenly generate a segmentation fault,
after which the binary (and other random files) have zero's in
them and are useless from then on. I.e., the binary which previously
would run, will no longer run, even after a reboot. At first I
though some buggy applications (which I'm running as *root*) were
screwing things up. This is still a possibility, but I ran
"rsync --checksum" against the original disk and found a bunch
of recently copied .a and .h files which were also affected. I'll
try to narrow down the conditions which cause this...
Be seeing you,