From: Joe Landman <landman@scalableinformatics.com>
To: xfs@oss.sgi.com
Subject: Re: sync() in 2.6.38.5
Date: Tue, 29 Nov 2011 14:33:40 -0500 [thread overview]
Message-ID: <4ED53394.2010100@scalableinformatics.com> (raw)
In-Reply-To: <CAOO4vO6sSFBxXXK1z018=ekEZpcpnZ5NT_xe3d503NjN3aHF5A@mail.gmail.com>
On 11/29/2011 02:17 PM, Paul Anderson wrote:
> Hi all,
>
> 2.6.38.5 (x64 intel, in todays case a 40TiByte SAN volume) appears to
> have a bug whereby not all active metadata will be flushed even on a
> quiescent machine (one that has nonetheless in the past been under
> very high load).
>
> We have tried several variations of clean shutdowns, combined with for
> example the "echo 3>/proc/sys/vm/drop_caches" trick to no avail - we
> still get lost files (well, 0 length files).
>
> We have several big servers scheduled to go down shortly, and I was
> wondering if there are other ideas besides just coping all recent data
> to another server.
Set your vm dirty time to small values. 1 second (100 centiseconds) or
so, among other things. You can also force the mount to be synchronous
(kills performance though).
Try
mount -o remount,sync /mountpoint
# not sure if this works with xfs though ...
sysctl -w vm.dirty_writeback_centisecs=100
sysctl -w vm.dirty_expire_centisecs=100
sysctl -w vm.dirty_ratio=1
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: landman@scalableinformatics.com
web : http://scalableinformatics.com
http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax : +1 866 888 3112
cell : +1 734 612 4615
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-29 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 19:17 sync() in 2.6.38.5 Paul Anderson
2011-11-29 19:33 ` Joe Landman [this message]
2011-11-29 19:35 ` Christoph Hellwig
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=4ED53394.2010100@scalableinformatics.com \
--to=landman@scalableinformatics.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.