From: Dmitry Monakhov <dmonakhov@openvz.org>
To: dave@jikos.cz
Cc: linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com, tytso@mit.edu,
hch@lst.de, aelder@sgi.com
Subject: Re: [PATCH 6/9] xfstests: add a new test that runs fsstress under ENOSPC conditions
Date: Mon, 07 Nov 2011 17:31:11 +0400 [thread overview]
Message-ID: <87sjm0kqjk.fsf@dmbot.sw.ru> (raw)
In-Reply-To: <20111107132533.GP12759@twin.jikos.cz>
On Mon, 7 Nov 2011 14:25:33 +0100, David Sterba <dave@jikos.cz> wrote:
> Hi,
>
> I saw this while running the newly added tests on btrfs:
>
> On Thu, Nov 03, 2011 at 09:55:50PM +0400, Dmitry Monakhov wrote:
> > --- /dev/null
> > +++ b/269
> > +_workout()
> > +{
> > + echo ""
> > + echo "Run fsstress"
> > + echo ""
> > + num_iterations=10
> > + enospc_time=2
> > + out=$SCRATCH_MNT/fsstress.$$
> > + args="-p128 -n999999999 -f setattr=1 $FSSTRESS_AVOID -d $out"
> > + echo "fsstress $args" >> $here/$seq.full
> > + $FSSTRESS_PROG $args > /dev/null 2>&1 &
> > + pid=$!
> > + echo "Run dd writers in parallel"
> > + for ((i=0; i < num_iterations; i++))
> > + do
> > + # File will be opened with O_TRUNC each time
> > + dd if=/dev/zero of=$SCRATCH_MNT/SPACE_CONSUMER bs=1M count=1 \
> > + > /dev/null 2>&1
> > + sleep $enospc_time
> > + done
> > + kill $pid
>
> 269 [failed, exit status 1] - output mismatch (see 269.out.bad)
> --- 269.out 2011-11-07 13:26:23.000000000 +0100
> +++ 269.out.bad 2011-11-07 14:07:44.000000000 +0100
> @@ -3,3 +3,4 @@
> Run fsstress
>
> Run dd writers in parallel
> +./269: line 60: kill: (9754) - No such process
>
> > + wait $pid
> > +}
>
> and the test is reported to fail. Seems that the dd commands finish in less 2
> seconds.
Have you recompile fsstress via make?
test explicitly want use new feature "-f setattr=1"
>
>
> david
> --
> 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
next prev parent reply other threads:[~2011-11-07 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 17:55 [PATCH 1/9] xfstests: fsstress add command line style output for show_opts Dmitry Monakhov
2011-11-03 17:55 ` [PATCH 2/9] xfstests: freeze fsstress options for 117'th Dmitry Monakhov
2011-11-03 17:55 ` [PATCH 3/9] xfstests: add fallocate support to fsstress Dmitry Monakhov
2011-11-03 17:55 ` [PATCH 4/9] xfstests: fsstress add FS_IOC_{SET, GET}FLAGS operations v2 Dmitry Monakhov
2011-11-03 17:55 ` [PATCH 5/9] xfstests: add fiemap operation to fsstress Dmitry Monakhov
2011-11-03 17:55 ` [PATCH 6/9] xfstests: add a new test that runs fsstress under ENOSPC conditions Dmitry Monakhov
2011-11-07 13:25 ` David Sterba
2011-11-07 13:31 ` Dmitry Monakhov [this message]
2011-11-08 17:01 ` David Sterba
2011-11-08 17:04 ` Christoph Hellwig
2011-11-03 17:55 ` [PATCH 7/9] xfstests: add a new quota " Dmitry Monakhov
2011-11-03 19:39 ` Christoph Hellwig
2011-11-07 6:15 ` Dmitry Monakhov
2011-11-03 17:55 ` [PATCH 8/9] xfstress: add regression testcase for d583fb87a3ff0 Dmitry Monakhov
2011-11-03 17:55 ` [PATCH 9/9] xfstress: Test data journaling flag switch for a single file Dmitry Monakhov
2011-11-07 20:52 ` [PATCH 1/9] xfstests: fsstress add command line style output for show_opts Dave Chinner
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=87sjm0kqjk.fsf@dmbot.sw.ru \
--to=dmonakhov@openvz.org \
--cc=aelder@sgi.com \
--cc=dave@jikos.cz \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--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