From: Dave Chinner <david@fromorbit.com>
To: "Linda A. Walsh" <lkml@tlinx.org>
Cc: PXXdraig Brady <P@draigBrady.com>,
LKML <linux-kernel@vger.kernel.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: write 'O_DIRECT' file w/odd amount of data: desirable result?
Date: Thu, 24 Feb 2011 20:26:25 +1100 [thread overview]
Message-ID: <20110224092625.GA3087@dastard> (raw)
In-Reply-To: <4D654C2E.2000703@tlinx.org>
On Wed, Feb 23, 2011 at 10:04:30AM -0800, Linda A. Walsh wrote:
>
>
> FWIW -- xfs-oss, included as 'last line' was of minor interest; known bug on
> this kernel?:
> Linux Ishtar 2.6.35.7-T610-Vanilla-1 #2 SMP PREEMPT Mon Oct 11
> 17:19:41 PDT 2010 x86_64 x86_64 x86_64 GNU/Linux
....
> Of *SIGNIFICANT* note. In trying to create an empty file of the size
> used, from scratch, using 'xfs_mkfile', I got an error:
>
> > xfs_mkfile 5776419696 testfile
> pwrite64: Invalid argument
xfs_mkfile does not create an "empty" file. It creates a file that
is full of zeros.
iAnd you're getting that erro because:
5776419696 / 512 = 11,282,069.7188
the last write is not a multiple of the sector size and xfs_mkfile
uses direct IO. It has always failed when you try to do this. If you
want to create allocated, zeroed files of abitrary size, then use:
xfs_io -f -c "truncate $size" -c "resvsp 0 $size" $filename
to preallocate it. it'll be much, much faster than xfs_mkfile.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2011-02-24 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 4:30 write 'O_DIRECT' file w/odd amount of data: desirable result? Linda Walsh
2011-02-23 10:34 ` Pádraig Brady
[not found] ` <4D654C2E.2000703@tlinx.org>
2011-02-24 1:18 ` Pádraig Brady
2011-02-24 9:26 ` Dave Chinner [this message]
2011-03-02 2:27 ` RFE kernel option to do the desirable thing, w/regards to 'O_DIRECT' and mis-aligned data Linda Walsh
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=20110224092625.GA3087@dastard \
--to=david@fromorbit.com \
--cc=P@draigBrady.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox