public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: hch@infradead.org, ext4 development <linux-ext4@vger.kernel.org>,
	Jan Kara <jack@suse.cz>,
	xfs@oss.sgi.com
Subject: Re: [PATCH 4/8] Add test of quota accounting using fsx
Date: Tue, 27 Jul 2010 10:48:48 +0200	[thread overview]
Message-ID: <20100727084848.GC3358@quack.suse.cz> (raw)
In-Reply-To: <20100727081538.GB3358@quack.suse.cz>

On Tue 27-07-10 10:15:38, Jan Kara wrote:
> On Mon 26-07-10 16:46:17, Eric Sandeen wrote:
> > On 06/15/2010 04:55 AM, Jan Kara wrote:
> > > On Wed 09-06-10 12:49:49, Eric Sandeen wrote:
> > >> Jan Kara wrote:
> > >>> Run fsx (and also several fsx threads in parallel) and verify that
> > >>> quota accounting is correct after they finish.
> > >>
> > >> Jan, I'm having trouble with this one on XFS for some reason, with our 
> > >> RHEL6 kernel and quota-3.17...
> > >   OK, attached is an improvement to the XFSQA tests after which all quota
> > > tests pass for XFS just fine.
> > >   The second patch is just minor general improvement of _require_scratch
> > > macro.
> > >   Could they be added to XFSQA repository? Thanks.
> > 
> > Jan, I've got some ext4 failures reported on these, although I can't hit
> > them, so not quite sure what's going on.
> > 
> > In 231:
> > 
> > +< fsgqa     --     760       0       0              3     0     0
> > +---
> > +> fsgqa     --     764       0       0              3     0     0
> > +14c14
> > +< fsgqa     --     760       0       0              3     0     0
> > +---
> > +> fsgqa     --     764       0       0              3     0     0
> > 
> > after the quotacheck & repquota we have 4 more blocks.  Maybe this
> > is due to my accounting of metadata blocks at write time, and not
> > before ... would it be reasonable to put a sync call as the first
> > line of check_usage() ?
>   Just last week a change went into xfstests which introduces a generic
> quota checking function and uses sync before getting quota usage. I think
> xfstests passed for me with ext4 after this change but I've now restarted
> the tests to recheck it.
  For me all the quota tests pass just fine with ext4 and the latest
xfstests... So does the latest version work also for you?

									Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-07-27  8:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 14:14 [PATCH 0/8 v3] Quota tests for XFSQA Jan Kara
2010-05-24 14:14 ` [PATCH 1/8] Fix test whether kernel supports quotas Jan Kara
2010-05-24 14:14 ` [PATCH 2/8] Fix fallocate() test Jan Kara
2010-05-24 14:14 ` [PATCH 3/8] Test basic quota enforcement Jan Kara
2010-05-25 10:06   ` Christoph Hellwig
2010-05-25 14:41     ` Jan Kara
2010-05-25 20:39     ` Jan Kara
2010-05-27 16:30       ` Christoph Hellwig
2010-05-27 17:08         ` Jan Kara
2010-05-24 14:14 ` [PATCH 4/8] Add test of quota accounting using fsx Jan Kara
2010-06-09 17:49   ` Eric Sandeen
2010-06-10 10:58     ` Jan Kara
2010-06-10 16:50       ` Eric Sandeen
2010-06-10 20:43         ` Eric Sandeen
2010-06-14 12:46           ` Jan Kara
2010-06-14 10:48         ` Jan Kara
2010-06-15  9:55     ` Jan Kara
2010-07-26 21:46       ` Eric Sandeen
2010-07-27  8:15         ` Jan Kara
2010-07-27  8:48           ` Jan Kara [this message]
2010-07-27 13:11             ` Eric Sandeen
2010-05-24 14:14 ` [PATCH 5/8] Add quota test with fsstress Jan Kara
2010-05-24 14:14 ` [PATCH 6/8] Add quota accounting test when fsstress is run and quota limits are set low Jan Kara
2010-05-24 14:14 ` [PATCH 7/8] Add test of quota limit and info setting Jan Kara
2010-05-24 14:14 ` [PATCH 8/8] Add test for quota accounting after remount read only Jan Kara

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=20100727084848.GC3358@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=hch@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox