From: Matthias Schniedermeyer <ms@citd.de>
To: troby <Thorn.Roby@harlandfs.com>
Cc: xfs@oss.sgi.com
Subject: Re: How to pre-allocate files for sequential access?
Date: Thu, 5 Apr 2012 23:57:55 +0200 [thread overview]
Message-ID: <20120405215755.GA18725@citd.de> (raw)
In-Reply-To: <33564834.post@talk.nabble.com>
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.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-05 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 23:57 How to pre-allocate files for sequential access? troby
2012-04-05 15:40 ` Eric Sandeen
2012-04-05 21:57 ` Matthias Schniedermeyer [this message]
2012-04-05 22:40 ` Eric Sandeen
2012-04-06 7:06 ` Stan Hoeppner
2012-04-10 19:12 ` troby
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=20120405215755.GA18725@citd.de \
--to=ms@citd.de \
--cc=Thorn.Roby@harlandfs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.