public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: hch@infradead.org, sandeen@redhat.com, jack@suse.cz, xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] xfstests-dev: More stress tests
Date: Thu, 27 May 2010 19:35:09 +0200	[thread overview]
Message-ID: <20100527173508.GD3576@quack.suse.cz> (raw)
In-Reply-To: <1274977524-19741-1-git-send-email-dmonakhov@openvz.org>

On Thu 27-05-10 20:25:22, Dmitry Monakhov wrote:
> I've finally port my tests to common platform with respect to previous
> comments. Pathes agains Jen's xfstest tree
> 
> *Tests state*
> I've executed it on ext4 on current ext4.git/next snapshot and
> with http://patchwork.ozlabs.org/patch/53720/
> 
> 0001) Is now succeed finally.(i've found more than 5 bugs with that testcase)
> 
> 0002) Is failed by now:
>       Sometimes it failed due to quota leak (dont know where yet)
  I sometimes observe that quota accounting is wrong on ext4 in my fsstress
test as well...

>       Sometimes kernel hungs with following call trace:
>       sys_quotactl
>       ->do_quotactl
>         ->vfs_quota_off
>           ->vfs_quota_disable
>             ->invalidate_dquots()
>               /* Wait here for a dqput */
>      Seems what we have dquot leakage.
> Still digging...
  Hmm, interesting. I don't have a clue where that could happen.

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

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

      parent reply	other threads:[~2010-05-27 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 16:25 [PATCH 0/2] xfstests-dev: More stress tests Dmitry Monakhov
2010-05-27 16:25 ` [PATCH 1/2] xfstests-dev: add one more stress test Dmitry Monakhov
2010-05-27 16:25   ` [PATCH 2/2] xfstests-dev: Add one more quota " Dmitry Monakhov
2010-05-27 17:35 ` Jan Kara [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=20100527173508.GD3576@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=dmonakhov@openvz.org \
    --cc=hch@infradead.org \
    --cc=sandeen@redhat.com \
    --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