From: Joe Landman <joe.landman@gmail.com>
To: xfs@oss.sgi.com
Subject: Re: XFS write cache flush policy
Date: Sat, 08 Dec 2012 14:51:11 -0500 [thread overview]
Message-ID: <50C39A2F.8090006@gmail.com> (raw)
In-Reply-To: <5955806.tSHc7WOiJd@saturn>
On 12/08/2012 02:40 PM, Michael Monnerie wrote:
> Am Samstag, 8. Dezember 2012, 20:29:27 schrieb Matthias Schniedermeyer:
>> I have the same problem, several times.
>
> I'd like to chime in here, with a similar issue: I have Linux on my
> desktop, xfs is the home partition, 16G RAM. One day my system froze, no
> chance to do a buffer flush via SYS-S/U/B, I had to press the reset
> button (no power off, just reset). Upon restart, *lots* of files were
> gone, destroyed, etc, and my KDE desktop wouldn't work anymore. Luckily
> I have backups, and could restore - but this just shouldn't happen, and
> it was *much* better with older kernels. What is the problem that
> metadata isn't written to disk occasionally? I was on 3.6.6 when that
> happened, now on 3.6.8, so very recent.
I am not sure this is xfs specific ... I think I've had this problem on
ext3 in the 3.x (x >= 5) region ... though I am trying to disambiguate
this from an mdadm 3.2.6 bug.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-12-08 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 8:51 XFS write cache flush policy Lin Li
2012-12-08 19:29 ` Matthias Schniedermeyer
2012-12-08 19:40 ` Michael Monnerie
2012-12-08 19:51 ` Joe Landman [this message]
2012-12-08 19:53 ` Matthias Schniedermeyer
2012-12-09 7:19 ` Lin Li
2012-12-10 1:01 ` Dave Chinner
2012-12-10 20:14 ` Michael Monnerie
2012-12-10 0:58 ` Dave Chinner
2012-12-10 9:12 ` Matthias Schniedermeyer
2012-12-10 20:54 ` Eric Sandeen
2012-12-10 21:45 ` Matthias Schniedermeyer
2012-12-11 0:25 ` Dave Chinner
2012-12-10 0:45 ` Dave Chinner
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=50C39A2F.8090006@gmail.com \
--to=joe.landman@gmail.com \
--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