From: Christoph Hellwig <hch@infradead.org>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com, hch@lst.de,
aelder@sgi.com
Subject: Re: [PATCH 7/8] xfstests: add a new test that runs fsstress under ENOSPC conditions
Date: Wed, 2 Nov 2011 15:53:58 -0400 [thread overview]
Message-ID: <20111102195357.GA22500@infradead.org> (raw)
In-Reply-To: <1319849297-3506-8-git-send-email-dmonakhov@openvz.org>
On Sat, Oct 29, 2011 at 04:48:16AM +0400, Dmitry Monakhov wrote:
> During stress testing we want to cover as much code paths as possible
> fsstress is very good for this purpose. But it has expandable nature
> (disk usage almost continually grow). So once it goes in no ENOSPC
> condition it will be where till the end. But by running 'dd' writers
> in parallel we can regularly trigger ENOSPC but only for a limited
> periods of time because each time it opens the same file with O_TRUNC.
This fails for me on XFS because the fsstress process has already
finished by the time you try to kill it:
--- 266.out 2011-11-02 19:46:27.000000000 +0000
+++ 266.out.bad 2011-11-02 19:48:33.000000000 +0000
@@ -3,3 +3,4 @@
Run fsstress
Run dd writers in parallel
+./266: line 60: kill: (3403) - No such process
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel@vger.kernel.org, aelder@sgi.com, hch@lst.de,
xfs@oss.sgi.com
Subject: Re: [PATCH 7/8] xfstests: add a new test that runs fsstress under ENOSPC conditions
Date: Wed, 2 Nov 2011 15:53:58 -0400 [thread overview]
Message-ID: <20111102195357.GA22500@infradead.org> (raw)
In-Reply-To: <1319849297-3506-8-git-send-email-dmonakhov@openvz.org>
On Sat, Oct 29, 2011 at 04:48:16AM +0400, Dmitry Monakhov wrote:
> During stress testing we want to cover as much code paths as possible
> fsstress is very good for this purpose. But it has expandable nature
> (disk usage almost continually grow). So once it goes in no ENOSPC
> condition it will be where till the end. But by running 'dd' writers
> in parallel we can regularly trigger ENOSPC but only for a limited
> periods of time because each time it opens the same file with O_TRUNC.
This fails for me on XFS because the fsstress process has already
finished by the time you try to kill it:
--- 266.out 2011-11-02 19:46:27.000000000 +0000
+++ 266.out.bad 2011-11-02 19:48:33.000000000 +0000
@@ -3,3 +3,4 @@
Run fsstress
Run dd writers in parallel
+./266: line 60: kill: (3403) - No such process
next prev parent reply other threads:[~2011-11-02 19:54 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
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 [this message]
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=20111102195357.GA22500@infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--cc=dmonakhov@openvz.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.