On 14 Jan, Eric Sandeen wrote:
> Hi Joy -
>
> Hm, I have never seen file versions from "a few days back" - usually on
> a lock-up, you only have problems with files written in the last ~30
> seconds - and then, you don't get the old version back, anyway.
If a hd/fs-driver locks up, write() might return and data stays in
cache, after some time the machine runs out of memory/buffer space and
alla processes that tryes to write() hangs in a syscall (non killable).
I have seen this on a e2fs system that had a broken
filesystem-struckture.
Jonas
--
http://wiss.unx.nu
http://linux.unx.nu
Another Glitch in the Call
We don't need no indirection
We don't need no flow control
No data typing or declarations
Did you leave the lists alone?
Hey! Hacker! Leave those lists alone!
Chorus:
All in all, it's just a pure-LISP function call.
All in all, it's just a pure-LISP function call.
|