[Top] [All Lists]

Re: Files not touched in weeks got truncated after a crash

To: xfs@xxxxxxxxxxx
Subject: Re: Files not touched in weeks got truncated after a crash
From: Guido Winkelmann <guido@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 14 Nov 2013 11:11:12 +0100
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <CAAxjCEz5ncQGfpZTfeps1r+U0q8E26P5_t6Mk_QP4FekvbRivA@xxxxxxxxxxxxxx>
References: <2662179.4mj0dgORXu@r008> <5283E387.70704@xxxxxxxxx> <CAAxjCEz5ncQGfpZTfeps1r+U0q8E26P5_t6Mk_QP4FekvbRivA@xxxxxxxxxxxxxx>
User-agent: KMail/4.10.5 (Linux/3.10.17-gentoo; KDE/4.10.5; x86_64; ; )
On Wednesday 13 November 2013 22:43:23 Stefan Ring wrote:
>On Wed, Nov 13, 2013 at 9:39 PM, Ric Wheeler <ricwheeler@xxxxxxxxx> wrote:
>> You should update your kernel - this sounds like an issue that Dave fixed
>> quite a few months back (and got shipped in RHEL and other distros, I don't
>> know about when Centos would pick it up)
>It's in the CentOS 6.4 kernel, according to the release notes:
>/html/6.4_Technical_Notes/kernel.html (BZ#855139)

Hm, this could be it, but it still sounds a bit unlikely.
The bug description implies that the filesystem would have to have been idling 
from the point where the affected files were written until the point of the 
system crash (or unclean unmount), such that the old, and by that time 
incorrect, metadata updates would still linger in the journal, but that was 
not really the case here. The filesystem was quite busy during those weeks....

Also, the bug report speaks only of zero-length files, while many of our files 
had been truncated to lengths other than zero.


<Prev in Thread] Current Thread [Next in Thread>