From: Bruce Cran <bruce@cran.org.uk>
To: Greg Sullivan <greg.sullivan@sullivang.net>
Cc: fio@vger.kernel.org
Subject: Re: Test files being created twice as large as requested (Win7)
Date: Fri, 17 Aug 2012 13:26:37 +0100 [thread overview]
Message-ID: <502E387D.9030901@cran.org.uk> (raw)
In-Reply-To: <CAHaS=QxT7Prz4jw8b5rZ-D3gTmejFp3D6ZA6DxcigHpEcVAJbw@mail.gmail.com>
On 16/08/2012 04:34, Greg Sullivan wrote:
> fio seems to be creating test files that are twice as large as
> requested.
The problem is that posix_fallocate isn't resetting the file pointer, so
writes start at the end of the file.
I'll look over the Windows code to make sure there aren't any similar
problems and create a new build.
--
Bruce Cran
next prev parent reply other threads:[~2012-08-17 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 3:34 Test files being created twice as large as requested (Win7) Greg Sullivan
2012-08-17 6:28 ` Jens Axboe
2012-08-17 11:24 ` Greg Sullivan
2012-08-17 11:29 ` Jens Axboe
2012-08-17 12:26 ` Bruce Cran [this message]
2012-08-17 12:33 ` Greg Sullivan
2012-08-17 12:45 ` Bruce Cran
2012-08-17 13:36 ` Bruce Cran
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=502E387D.9030901@cran.org.uk \
--to=bruce@cran.org.uk \
--cc=fio@vger.kernel.org \
--cc=greg.sullivan@sullivang.net \
/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