linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: linux-xfs@vger.kernel.org
Subject: Re: Do we need a way to force xfsaild to run?
Date: Thu, 18 May 2017 08:57:30 -0700	[thread overview]
Message-ID: <20170518155730.GY4519@birch.djwong.org> (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.
> 
> My specific use case is while testing the code I've been working on for the
> buffer retry stuff, where, I need to wait xfsaild to run to trigger the bug,
> adding a way to force it, in this case at least, would be useful for me, I could
> work on that, but only if somebody else can actually think this to be
> interesting, adding a new xfsctl just for 'me' does not sound worth the time :)
> 
> Anybody else might have interest on it or maybe this is just a waste of time?

"Run" the xfsaild as in 'push all the AIL items out to disk'?

I think xfs_freeze -f (followed immediately by xfs_freeze -u) will push
the AIL as part of the freezing process... though that might be more
work than you're looking for...?

--D

> 
> Cheers
> 
> -- 
> Carlos
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-05-18 15:57 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 [this message]
2017-05-19  0:16 ` 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=20170518155730.GY4519@birch.djwong.org \
    --to=darrick.wong@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).