Ingo Bormuth wrote:
On 2007-05-30 15:03, David Masover wrote:
Only, recently, these fsck-a-thons started happening more and more often, and
I started to lose random files. They'd just be silently truncated to 0 bytes.
And not files I was writing a lot -- I'm talking about things
like /bin/mount.
Hm, same here. I lost /bin/sleep several times.
Would you please describe the problem in more details?
What kernel version? What does "I lost /bin/sleep" mean?
Does it mean that:
1. /bin/sleep was truncated to 0 bytes, i.e. "ls -l /bin/sleep" shows
something like
-rwxr-xr-x 1 root root 0 2005-04-20 18:32 /bin/sleep
2. /bin/sleep disappeared ("ls -l /bin" doesn't show this file)
3. /bin/sleep exists, but filled by zeros
etc...
Thanks,
Edward.
I have a little script
printing status messages to the screen, sleeping two seconds and print
again - you name it. The probability that /bin/sleep is accessed at the
same time the system crashes is quite high (this is _no_ write access,
the system is even mounted noatime).
How could pure execution of a file cause corruption of the file itself?
Any idea ?
Apart from that single file, I never had any serious problems with
reiser4 on three busy systems for years - fsck.reiser4 works like charme.
