From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: Re: Do we need a way to force xfsaild to run?
Date: Fri, 19 May 2017 10:16:34 +1000 [thread overview]
Message-ID: <20170519001634.GR17542@dastard> (raw)
In-Reply-To: <20170518142159.gkr6be4dralc6xiq@eorzea.usersys.redhat.com>
On Thu, May 18, 2017 at 04:21:59PM +0200, Carlos Maiolino wrote:
> Hi,
>
> This is something I was thinking while working on that buffer retry stuff.
>
> Currently, we have no way to force xfsaild to run, and I was wondering if
> somebody has any opinion if it would be useful to create a new xfsctl, to start
> xfsaild for debugging purposes, using xfs_io to trigger it.
THere's lots of ways to trigger it to run. You can do it on demand
via a freeze or remount-ro or by filling up the log, or get it to
run every second automatically iso there's no wait time at all by
turning /proc/sys/fs/xfs/xfssyncd_centiseconds down to the minimum.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2017-05-19 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 14:21 Do we need a way to force xfsaild to run? Carlos Maiolino
2017-05-18 14:32 ` Shan Hai
2017-05-18 15:57 ` Darrick J. Wong
2017-05-19 0:16 ` Dave Chinner [this message]
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=20170519001634.GR17542@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/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.