linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Do we need a way to force xfsaild to run?
@ 2017-05-18 14:21 Carlos Maiolino
  2017-05-18 14:32 ` Shan Hai
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Carlos Maiolino @ 2017-05-18 14:21 UTC (permalink / raw)
  To: linux-xfs

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?

Cheers

-- 
Carlos

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Do we need a way to force xfsaild to run?
  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
  2 siblings, 0 replies; 4+ messages in thread
From: Shan Hai @ 2017-05-18 14:32 UTC (permalink / raw)
  To: linux-xfs



On 2017年05月18日 22:21, 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 :)

For the debugging purpose how about mkfs with a small size of log
for instance 50MB and then use benchmark tools like fs_mark to
fill the log quickly(write lots of small files instead of a single
huge file), then the xfsaild will run frequently :)

Thanks
Shan Hai
> Anybody else might have interest on it or maybe this is just a waste of time?
>
> Cheers
>


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Do we need a way to force xfsaild to run?
  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
  2 siblings, 0 replies; 4+ messages in thread
From: Darrick J. Wong @ 2017-05-18 15:57 UTC (permalink / raw)
  To: linux-xfs

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Do we need a way to force xfsaild to run?
  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
  2 siblings, 0 replies; 4+ messages in thread
From: Dave Chinner @ 2017-05-19  0:16 UTC (permalink / raw)
  To: linux-xfs

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-05-19  0:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).