All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com, hch@lst.de,
	aelder@sgi.com
Subject: Re: [PATCH 6/8] xfstests: add fiemap operation to fsstress
Date: Thu, 03 Nov 2011 16:14:04 +0400	[thread overview]
Message-ID: <87ty6lxv1v.fsf@dmbot.sw.ru> (raw)
In-Reply-To: <87zkgdy2fi.fsf@dmbot.sw.ru>

On Thu, 03 Nov 2011 13:34:41 +0400, Dmitry Monakhov <dmonakhov@openvz.org> wrote:
> On Wed, 2 Nov 2011 15:55:34 -0400, Christoph Hellwig <hch@infradead.org> wrote:
> > On Sat, Oct 29, 2011 at 04:48:15AM +0400, Dmitry Monakhov wrote:
> > > Related bug: http://patchwork.ozlabs.org/patch/118863
> > > 
> > > Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> > 
> > This causes a very weird XFS failure in test 117 for me.  While it
> > obviously is an xfs bug that you uncovered (good!) I'm a bit worried
> > about simply enabling operations in existing tests.
> Ohh. i've got what your are talking about. We can not add new ops
> for tests there seed is passed explicitly. And yes i've braked this, but
> this is because such frozen tests was written in not determined
> way :). Good determined test should has not just seed opt, but also
> explicit set of operations. All others (non determined) tests which use
> fsstress may benefit from new ops. So I'll redo my patch queue like this:
> 1) Add explicit option set for all frozen tests
i've stuck immediately on first test ;(.
on my kernel 107'th test always failed (commit: 73a57c642cdfa660
"1.1.0 release"), is it expected? Which xfs-tree and commit should i use?
> 2) Add new features to fssstress with non zero probability. 
> > 
> > Alex, Eric, Dave - should we add new tests with the new operations
> > Dmitry added, or is adding new ops to the existing tests fine?
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, aelder@sgi.com, hch@lst.de,
	xfs@oss.sgi.com
Subject: Re: [PATCH 6/8] xfstests: add fiemap operation to fsstress
Date: Thu, 03 Nov 2011 16:14:04 +0400	[thread overview]
Message-ID: <87ty6lxv1v.fsf@dmbot.sw.ru> (raw)
In-Reply-To: <87zkgdy2fi.fsf@dmbot.sw.ru>

On Thu, 03 Nov 2011 13:34:41 +0400, Dmitry Monakhov <dmonakhov@openvz.org> wrote:
> On Wed, 2 Nov 2011 15:55:34 -0400, Christoph Hellwig <hch@infradead.org> wrote:
> > On Sat, Oct 29, 2011 at 04:48:15AM +0400, Dmitry Monakhov wrote:
> > > Related bug: http://patchwork.ozlabs.org/patch/118863
> > > 
> > > Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> > 
> > This causes a very weird XFS failure in test 117 for me.  While it
> > obviously is an xfs bug that you uncovered (good!) I'm a bit worried
> > about simply enabling operations in existing tests.
> Ohh. i've got what your are talking about. We can not add new ops
> for tests there seed is passed explicitly. And yes i've braked this, but
> this is because such frozen tests was written in not determined
> way :). Good determined test should has not just seed opt, but also
> explicit set of operations. All others (non determined) tests which use
> fsstress may benefit from new ops. So I'll redo my patch queue like this:
> 1) Add explicit option set for all frozen tests
i've stuck immediately on first test ;(.
on my kernel 107'th test always failed (commit: 73a57c642cdfa660
"1.1.0 release"), is it expected? Which xfs-tree and commit should i use?
> 2) Add new features to fssstress with non zero probability. 
> > 
> > Alex, Eric, Dave - should we add new tests with the new operations
> > Dmitry added, or is adding new ops to the existing tests fine?
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-11-03 12:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29  0:48 [PATCH 0/8] xfstests: Bunch of new stress tests -v3 Dmitry Monakhov
2011-10-29  0:48 ` Dmitry Monakhov
2011-10-29  0:48 ` [PATCH 1/8] xfstests: fsstress dump inode info when possible Dmitry Monakhov
2011-10-29  0:48   ` Dmitry Monakhov
2011-10-29  0:48 ` [PATCH 2/8] xfstests: add different logging option to fsstress Dmitry Monakhov
2011-10-29  0:48   ` Dmitry Monakhov
2011-10-29  0:48 ` [PATCH 3/8] xfstests: fsstress should kill children tasks before exit Dmitry Monakhov
2011-10-29  0:48   ` Dmitry Monakhov
2011-10-29  0:48 ` [PATCH 4/8] xfstests: add fallocate support to fsstress Dmitry Monakhov
2011-10-29  0:48   ` Dmitry Monakhov
2011-10-29  0:48 ` [PATCH 5/8] xfstests: fsstress add FS_IOC_{SET, GET}FLAGS operations v2 Dmitry Monakhov
2011-10-29  0:48   ` [PATCH 5/8] xfstests: fsstress add FS_IOC_{SET,GET}FLAGS " Dmitry Monakhov
2011-10-29  0:48 ` [PATCH 6/8] xfstests: add fiemap operation to fsstress Dmitry Monakhov
2011-10-29  0:48   ` Dmitry Monakhov
2011-11-02 19:55   ` Christoph Hellwig
2011-11-02 19:55     ` Christoph Hellwig
2011-11-03  9:34     ` Dmitry Monakhov
2011-11-03  9:34       ` Dmitry Monakhov
2011-11-03 12:14       ` Dmitry Monakhov [this message]
2011-11-03 12:14         ` Dmitry Monakhov
2011-11-03 12:28         ` Christoph Hellwig
2011-11-03 12:28           ` Christoph Hellwig
2011-11-03 10:54     ` Theodore Tso
2011-11-03 10:54       ` Theodore Tso
2011-11-03 11:04       ` Dmitry Monakhov
2011-11-03 11:04         ` Dmitry Monakhov
2011-11-03 16:05         ` Ted Ts'o
2011-11-03 16:05           ` Ted Ts'o
2011-10-29  0:48 ` [PATCH 7/8] xfstests: add a new test that runs fsstress under ENOSPC conditions Dmitry Monakhov
2011-10-29  0:48   ` Dmitry Monakhov
2011-11-02 19:53   ` Christoph Hellwig
2011-11-02 19:53     ` Christoph Hellwig
2011-11-02 20:36     ` Dmitry Monakhov
2011-11-02 20:36       ` Dmitry Monakhov
2011-11-02 21:06       ` Christoph Hellwig
2011-11-02 21:06         ` Christoph Hellwig
2011-10-29  0:48 ` [PATCH 8/8] xfstests: add a new quota " Dmitry Monakhov
2011-10-29  0:48   ` Dmitry Monakhov

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=87ty6lxv1v.fsf@dmbot.sw.ru \
    --to=dmonakhov@openvz.org \
    --cc=aelder@sgi.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.