From: Guido Winkelmann <guido@ambient-entertainment.de>
To: xfs@oss.sgi.com
Subject: Re: Files not touched in weeks got truncated after a crash
Date: Thu, 14 Nov 2013 11:11:12 +0100 [thread overview]
Message-ID: <6414439.XpxSIk2GZ9@r008> (raw)
In-Reply-To: <CAAxjCEz5ncQGfpZTfeps1r+U0q8E26P5_t6Mk_QP4FekvbRivA@mail.gmail.com>
On Wednesday 13 November 2013 22:43:23 Stefan Ring wrote:
>On Wed, Nov 13, 2013 at 9:39 PM, Ric Wheeler <ricwheeler@gmail.com> 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:
>https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6
>/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.
Guido
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-11-14 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 16:36 Files not touched in weeks got truncated after a crash Guido Winkelmann
2013-11-13 16:51 ` Roger Willcocks
2013-11-14 10:25 ` Guido Winkelmann
2013-11-13 20:39 ` Ric Wheeler
2013-11-13 21:43 ` Stefan Ring
2013-11-14 10:11 ` Guido Winkelmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6414439.XpxSIk2GZ9@r008 \
--to=guido@ambient-entertainment.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox