At 10:26 17-5-2001 +0300, Lauri Ojantakanen wrote:
Hi,
I am very happy using xfs (converted everything to xfs:). Usually everything
goes fine with the system but there is one kinda scary thing: sometimes some
files seem to be getting filled with null's after recovery. I mean that after
one recovery one opera's bookmark file was still there but the contents of
the file was just '\0'. File was not truncated but its contents were "gone".
I just would like to know whether this kind of behaviour is to be considered
as a feature rather than a bug. I also would like to know what I could do to
minimize the possibility for this to happen.
hmmm... I remember that at some point kupdate got stuck on my machine and I
could not reboot the machine or sync the filessystem.
If that happened I noticed that files that were edited ot touched after the
kupdate hung would get a "\0" in it after recovery. In the case of
/etc/fstab it gave some very weird results.
It took some time to notice because the rest of the system continued to
function.
The cause of it was eventually lead back to a bad ram stick.
The 2.2 kernel before that obviously was not pushing the ram hard enough to
expose it. I have not seen it after replacing the bad ram stick.
This may not be the case here but I am just giving a explanation of what I
did to make it produce those errors.
Cheers
--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.
|