From: Eric Sandeen <sandeen@sandeen.net>
To: Nathan Scott <nathans@aconex.com>
Cc: Jeff Zheng <Jeff.Zheng@endace.com>, xfs@oss.sgi.com
Subject: Re: Is persistant preallocation possible?
Date: Mon, 24 May 2010 22:19:52 -0500 [thread overview]
Message-ID: <4BFB41D8.3020402@sandeen.net> (raw)
In-Reply-To: <1374176788.272721274754374474.JavaMail.root@mail-au.aconex.com>
Nathan Scott wrote:
> ----- "Jeff Zheng" <Jeff.Zheng@endace.com> wrote:
>
>> Hi,
>>
>> We are trying to control where the files are being allocated on the
>> disks, and we tried xfs preallocation. What we found is that each time
>> the file being reopened the location of the pre-allocated space could
>> change (not all the time). Is there a way to do persistent
>> preallocation in xfs, like the same file will always be on the same
>> location on the disk given that the requested size doesn’t change?
>>
>
> Sounds like you are truncating the file (on open?), and hence discarding
> the preallocation. XFS preallocation is persistent already, so I think
> something you are doing must be discarding those preallocated extents.
>
> Could you post a test program, or sequence of xfs_io commands, that would
> demonstrate the problem?
>
> cheers.
>
... maybe you mean that truncating / pre-allocating the same space repeatedly
on the same filename ends up with blocks mapped in different locations...?
That's entirely expected... nothing about the preallocation interface lets
you "control *where* files are being allocated" as you said above...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-25 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 2:05 Is persistant preallocation possible? Jeff Zheng
2010-05-25 2:26 ` Nathan Scott
2010-05-25 3:19 ` Eric Sandeen [this message]
2010-05-25 12:33 ` Roger Willcocks
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=4BFB41D8.3020402@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Jeff.Zheng@endace.com \
--cc=nathans@aconex.com \
--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