public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Lin Li <sdeber@gmail.com>
Subject: Re: XFS write cache flush policy
Date: Sat, 08 Dec 2012 20:40:07 +0100	[thread overview]
Message-ID: <5955806.tSHc7WOiJd@saturn> (raw)
In-Reply-To: <20121208192927.GA17875@citd.de>


[-- Attachment #1.1: Type: text/plain, Size: 1117 bytes --]

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.

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
XING: https://www.xing.com/profile/Michael_Monnerie
Twitter: @MichaelMonnerie https://twitter.com/MichaelMonnerie
FaceBook: https://www.facebook.com/michael.monnerie
LinkedIn: http://lnkd.in/uGx6ug

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-12-08 19:37 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 [this message]
2012-12-08 19:51     ` Joe Landman
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=5955806.tSHc7WOiJd@saturn \
    --to=michael.monnerie@is.it-management.at \
    --cc=sdeber@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