| To: | Steven Swanson <swanson@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Does XFS ever relocate extents after they are on disk? |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 14 Mar 2011 06:36:22 -0400 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <D03B8F30-7E6D-4C85-8160-9FB505E09B9F@xxxxxxxxxxx> |
| References: | <903E14DC-D9EA-4BDC-8D43-FBB9AB4127BC@xxxxxxxxxxx> <20110311100936.GA11879@xxxxxxxxxxxxx> <D03B8F30-7E6D-4C85-8160-9FB505E09B9F@xxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH v2] Check for immutable flag in fallocate path, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH v2] Check for immutable flag in fallocate path, Marco Stornelli |
| Previous by Thread: | Re: Does XFS ever relocate extents after they are on disk?, Steven Swanson |
| Next by Thread: | [next] xfs: error: called object 'panic' is not a function, Geert Uytterhoeven |
| Indexes: | [Date] [Thread] [Top] [All Lists] |