On Mon, Feb 16, 2009 at 20:02, Thibaut VARÈNE <[email protected]> wrote:
> Please don't remove the BTS from the CC-list. Bug report information must be
> recorded.

Didn't mean to remove Bts address: click on "Reply" instead of "Reply
to all" bt mistake.

> Le 16 févr. 09 à 19:26, Sandro Tosi a écrit :
>>
>> On Mon, Feb 16, 2009 at 19:19, Thibaut VARENE <[email protected]> wrote:
>>>
>>> What filesystem are you using on /var?
>>
>> xfs
>
> By default, XFS will zero-out inconsistent files after an unclean mount. If
> that's what happened, it's likely uptimed tried to use the (invalid) content
> of the file instead of its backup, which is why you didn't see anything in
> the log (when it uses its backup database it prints a message).

That might be what happened.

> Radek, I don't really know what to do about this. Working around filesystem
> issues is gonna be a burden. Adding supplementary checks to assert the
> validity of the file being read doesn't look really straightforward; do you
> have any suggestion about this? The way I see it, we could bail out in
> urec.c:231, and 1) give feedback on failure to read record entry, while 2)
> falling back to the backup database on such a failure... Of course, if the
> backup db is also damaged, we're doomed.

Fall back on the backup seems a smart move, of course in case both are
corrupted, starting from scratch is the only option at hand.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to