linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] xfstests/btrfs: add test for quota groups and drop snapshot
Date: Thu, 10 Jul 2014 21:31:07 +0000 (UTC)	[thread overview]
Message-ID: <pan$ca5c$23031d50$378e40$86a123f0@cox.net> (raw)
In-Reply-To: 20140710190055.GC5484@wotan.suse.de

Mark Fasheh posted on Thu, 10 Jul 2014 12:00:55 -0700 as excerpted:

> Given something like that, you'd just replace the calls to sleep with
> 'btrfs fi synctheworldandwait' and know that on return, the actions you
> just queued up completed.

I'll admit to not really knowing what I'm talking about here, but on 
first intuition, What about either btrfs filesystem sync calls, or 
mounting with the synctime (don't have time to look up the specific 
option ATM) mount option?  Normal sync is 30 seconds, but the mount 
option can be used to make that 5 seconds or whatever.  And I don't know 
whether btrfs filesystem sync is synchronous or not.

But that might help reduce it below 30 and 45 seconds, anyway, even if 
some sleep is still required.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  parent reply	other threads:[~2014-07-10 21:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 22:41 [PATCH] xfstests/btrfs: add test for quota groups and drop snapshot Mark Fasheh
2014-07-10  0:43 ` Dave Chinner
2014-07-10 17:36   ` Mark Fasheh
2014-07-10 18:32     ` Zach Brown
2014-07-10 19:00       ` Mark Fasheh
2014-07-10 19:05         ` Zach Brown
2014-07-10 19:24           ` Mark Fasheh
2014-07-10 21:31         ` Duncan [this message]
2014-07-22 18:10         ` David Sterba
2014-07-22 19:05         ` David Sterba
2014-07-23 12:30           ` David Sterba
2014-07-23 13:25             ` Josef Bacik
2014-07-10 21:10     ` Dave Chinner
2014-07-22 18:01 ` David Sterba

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='pan$ca5c$23031d50$378e40$86a123f0@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@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).