From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: XFS write cache flush policy
Date: Mon, 10 Dec 2012 21:14:47 +0100 [thread overview]
Message-ID: <1408451.5Ut0G7Wysl@saturn> (raw)
In-Reply-To: <5955806.tSHc7WOiJd@saturn>
[-- Attachment #1.1: Type: text/plain, Size: 1565 bytes --]
Am Samstag, 8. Dezember 2012, 20:40:07 schrieb Michael Monnerie:
> 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.
Similar problem yesterday: this time I could stop KDE, and get a root
session. Killed all processes by hand, because one xfs partition was
still open despite "lsof" not showing anything. At last there were only
a handful processes open, I killed "rsyncd", and suddenly disk I/O was
100%, looks like it was writing a lot of buffers, the disk was about 15s
in full activity. I've seen this strange behaviour before (lot and long
disk activity on reboot), but only now I could trace it down to rsyncd.
I have rsyncd running here as a target, my server is backuped here once
per night. So it's strange to see it having "something" open. I've moved
the backup target dir to another partition now, to see if I can see that
behaviour again.
--
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
next prev parent reply other threads:[~2012-12-10 20:12 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
2012-12-10 20:14 ` Michael Monnerie [this message]
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=1408451.5Ut0G7Wysl@saturn \
--to=michael.monnerie@is.it-management.at \
--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