From: Christoph Hellwig <hch@infradead.org>
To: Steven Swanson <swanson@cs.ucsd.edu>
Cc: xfs@oss.sgi.com
Subject: Re: Does XFS ever relocate extents after they are on disk?
Date: Mon, 14 Mar 2011 06:36:22 -0400 [thread overview]
Message-ID: <20110314103622.GA715@infradead.org> (raw)
In-Reply-To: <D03B8F30-7E6D-4C85-8160-9FB505E09B9F@cs.ucsd.edu>
On Fri, Mar 11, 2011 at 02:29:30PM -0800, Steven Swanson wrote:
> Christoph,
>
> Thanks for the quick reply.
>
> Here's another question: If I write data to an extent that already exists, am I also guaranteed that the new data will overwrite the same location? For instance, will XFS ever relocate an extent on a write in order to expand the extent?
Right now it won't. I wouldn't call that a guaranteed though - e.g. if
we're ever going to finish off storig file data in the inode for small
files we'll have to migrate them out of the inode once we create the
first extent.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-03-14 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 7:55 Does XFS ever relocate extents after they are on disk? Steven Swanson
2011-03-11 10:09 ` Christoph Hellwig
2011-03-11 22:29 ` Steven Swanson
2011-03-14 10:36 ` Christoph Hellwig [this message]
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=20110314103622.GA715@infradead.org \
--to=hch@infradead.org \
--cc=swanson@cs.ucsd.edu \
--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