On Thu, Sep 10, 2015 at 10:09:16PM +0200, Dušan Čolić wrote:
>
> There are various xfstests that try to fill up whole partition but
> they give false positives on file systems with transparent compression
> because they use compressible test files like input from /dev/zero.
> Different tests use different ways to generate test file(s) so what
> would be the preferred way to generate incompressible test files? Use
> /dev/urandom instead /dev/zero?
I would expect that most tests would use fallocate to allocate space
for ENOSPC tests, since it's much faster than writing all zeros.
If a file system with tansparent compression is treating space
allocated with fallocate as "all zeros" and hence infinitely
compressible, I'd argue that it's buggy, since one of the documented
uses of fallocate is to force the file system to allocate space so
that future writes are guaranteed to succeed, so that the application
doesn't have to deal with ENOSPC errors at some inconvenient time.
(For example, in the case of a DVR, you want to know that you've
allocated enough space for that all-so-critical recording of the
season finale of "The Big Bang Theory", or that episode of "Sex and
the City" which you had missed. :-)
Cheers,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
