From: Dave Chinner <david@fromorbit.com>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>,
Lin Li <sdeber@gmail.com>,
xfs@oss.sgi.com
Subject: Re: XFS write cache flush policy
Date: Mon, 10 Dec 2012 12:01:41 +1100 [thread overview]
Message-ID: <20121210010141.GH15784@dastard> (raw)
In-Reply-To: <20121208195304.GA20044@citd.de>
On Sat, Dec 08, 2012 at 08:53:04PM +0100, Matthias Schniedermeyer wrote:
> On 08.12.2012 20:40, 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.
>
> Now that you say it, this is what happend one of the other times,
> luckily i had done a backup just before i rebooted, so after
> xfs_repair'ing the partition (the only time i had to repair something
> for as long as i'm using XFS) i had to restore my home-directory from
> backup to get my desktop in a usable state again.
So the hard lockup caused your filesystem to be corrupted, and after
you ran repair lots of files were missing?
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
People, please be precise about what happened when reporting
problems. Random "me too" posts with ambiguous information in
them does not help solve problems.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-12-10 0:59 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
2012-12-08 19:53 ` Matthias Schniedermeyer
2012-12-09 7:19 ` Lin Li
2012-12-10 1:01 ` Dave Chinner [this message]
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=20121210010141.GH15784@dastard \
--to=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--cc=ms@citd.de \
--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