| To: | Matthias Schniedermeyer <ms@xxxxxxx> |
|---|---|
| Subject: | Re: How to pre-allocate files for sequential access? |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Thu, 5 Apr 2012 15:40:22 -0700 |
| Cc: | troby <Thorn.Roby@xxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <20120405215755.GA18725@xxxxxxx> |
| References: | <33564834.post@xxxxxxxxxxxxxxx> <20120405215755.GA18725@xxxxxxx> |
On Apr 5, 2012, at 2:57 PM, Matthias Schniedermeyer <ms@xxxxxxx> wrote: > On 04.04.2012 16:57, troby wrote: > > ... > > I think the easiest solution would be to create the said number of > files, but with dummy-filenames. > > Then write a script das does a xfs_bmap on each file, sorts them and > then renames the dummy-files to the correct-name in the order they are > on disc. > Inode64 will likely keep them in order without needing tricks like that. Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Roger Willcocks |
|---|---|
| Next by Date: | Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Peter Grandi |
| Previous by Thread: | Re: How to pre-allocate files for sequential access?, Matthias Schniedermeyer |
| Next by Thread: | Re: How to pre-allocate files for sequential access?, Stan Hoeppner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |