* Test 274 in xfstests
@ 2012-05-15 18:05 Jan Kara
2012-05-15 18:12 ` Eric Sandeen
0 siblings, 1 reply; 4+ messages in thread
From: Jan Kara @ 2012-05-15 18:05 UTC (permalink / raw)
To: wu.bo; +Cc: xfs
Hello,
test 274 fails e.g. for ext3 because it does not support fallocate(). So
I would think the best way to fix the is to add to the test
_require_xfs_io_falloc()
so that the test is run only for filesystems which do support fallocate.
But with that is connected one slightly related question - why does the
test use fallocate(1) binary instead of "xfs_io falloc" command which is
more common in xfstests?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Test 274 in xfstests
2012-05-15 18:05 Test 274 in xfstests Jan Kara
@ 2012-05-15 18:12 ` Eric Sandeen
2012-05-15 20:16 ` Jan Kara
0 siblings, 1 reply; 4+ messages in thread
From: Eric Sandeen @ 2012-05-15 18:12 UTC (permalink / raw)
To: Jan Kara; +Cc: wu.bo, xfs
On 5/15/12 1:05 PM, Jan Kara wrote:
> Hello,
>
> test 274 fails e.g. for ext3 because it does not support fallocate(). So
> I would think the best way to fix the is to add to the test
> _require_xfs_io_falloc()
> so that the test is run only for filesystems which do support fallocate.
> But with that is connected one slightly related question - why does the
> test use fallocate(1) binary instead of "xfs_io falloc" command which is
> more common in xfstests?
>
> Honza
Argh I'm behind. I had:
[PATCH V2] xfstests: several 274 fixups
on the list way too long ago.
Want to test that out? It has 1 review on the list, I'll merge it
soon - if you want to give it a quick test first, go for it :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Test 274 in xfstests
2012-05-15 18:12 ` Eric Sandeen
@ 2012-05-15 20:16 ` Jan Kara
2012-05-15 20:18 ` Eric Sandeen
0 siblings, 1 reply; 4+ messages in thread
From: Jan Kara @ 2012-05-15 20:16 UTC (permalink / raw)
To: Eric Sandeen; +Cc: wu.bo, Jan Kara, xfs
On Tue 15-05-12 13:12:21, Eric Sandeen wrote:
> On 5/15/12 1:05 PM, Jan Kara wrote:
> > Hello,
> >
> > test 274 fails e.g. for ext3 because it does not support fallocate(). So
> > I would think the best way to fix the is to add to the test
> > _require_xfs_io_falloc()
> > so that the test is run only for filesystems which do support fallocate.
> > But with that is connected one slightly related question - why does the
> > test use fallocate(1) binary instead of "xfs_io falloc" command which is
> > more common in xfstests?
> >
> > Honza
>
> Argh I'm behind. I had:
>
> [PATCH V2] xfstests: several 274 fixups
>
> on the list way too long ago.
>
> Want to test that out? It has 1 review on the list, I'll merge it
> soon - if you want to give it a quick test first, go for it :)
Yup, the patch works for me (since I'm mostly interested in ext3 not
being tested ;). I also reviewed your patch and it looks OK so feel free to
add:
Reviewed-by: Jan Kara <jack@suse.cz>
Just one comment. Messages like:
echo "Fill fs with 1M IOs; EIO expected" >> $seq.full
should probably speak of ENOSPC, not EIO, shouldn't they?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Test 274 in xfstests
2012-05-15 20:16 ` Jan Kara
@ 2012-05-15 20:18 ` Eric Sandeen
0 siblings, 0 replies; 4+ messages in thread
From: Eric Sandeen @ 2012-05-15 20:18 UTC (permalink / raw)
To: Jan Kara; +Cc: wu.bo, xfs
On 5/15/12 3:16 PM, Jan Kara wrote:
> On Tue 15-05-12 13:12:21, Eric Sandeen wrote:
>> On 5/15/12 1:05 PM, Jan Kara wrote:
>>> Hello,
>>>
>>> test 274 fails e.g. for ext3 because it does not support fallocate(). So
>>> I would think the best way to fix the is to add to the test
>>> _require_xfs_io_falloc()
>>> so that the test is run only for filesystems which do support fallocate.
>>> But with that is connected one slightly related question - why does the
>>> test use fallocate(1) binary instead of "xfs_io falloc" command which is
>>> more common in xfstests?
>>>
>>> Honza
>>
>> Argh I'm behind. I had:
>>
>> [PATCH V2] xfstests: several 274 fixups
>>
>> on the list way too long ago.
>>
>> Want to test that out? It has 1 review on the list, I'll merge it
>> soon - if you want to give it a quick test first, go for it :)
> Yup, the patch works for me (since I'm mostly interested in ext3 not
> being tested ;). I also reviewed your patch and it looks OK so feel free to
> add:
> Reviewed-by: Jan Kara <jack@suse.cz>
>
> Just one comment. Messages like:
> echo "Fill fs with 1M IOs; EIO expected" >> $seq.full
> should probably speak of ENOSPC, not EIO, shouldn't they?
Oh, yeah, whoops. thanks.
-Eric
> Honza
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-05-15 20:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-15 18:05 Test 274 in xfstests Jan Kara
2012-05-15 18:12 ` Eric Sandeen
2012-05-15 20:16 ` Jan Kara
2012-05-15 20:18 ` Eric Sandeen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox