From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: Contiguous file sequences
Date: Sat, 25 Sep 2010 11:42:31 +0200 [thread overview]
Message-ID: <201009251142.35467@zmi.at> (raw)
In-Reply-To: <4C9A6298.106@sandeen.net>
[-- Attachment #1.1: Type: Text/Plain, Size: 877 bytes --]
On Mittwoch, 22. September 2010 Eric Sandeen wrote:
> preallocation of each image before writing would help make it more
> likely that each image is itself contiguous (but again this is not
> -guaranteed-)
If all images were 1-2MB large, and if there is no parallel create, but
all images are copied after each other, wouldn't the mount option
"allocsize=2M" be sufficient to ensure pics are contigous? I guess XFS
would place them behind each other on disk, or why should there be gaps
between?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-25 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 11:01 Contiguous file sequences Daire Byrne
2010-09-22 20:10 ` Eric Sandeen
2010-09-24 10:43 ` Daire Byrne
2010-09-27 4:08 ` Eric Sandeen
2010-09-27 16:30 ` Daire Byrne
2010-09-27 18:35 ` Matthias Schniedermeyer
2010-09-28 1:16 ` Dave Chinner
2010-09-27 20:56 ` Roger Willcocks
2010-09-25 9:42 ` Michael Monnerie [this message]
2010-09-22 20:50 ` Matthias Schniedermeyer
2010-09-22 22:36 ` Dave Chinner
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=201009251142.35467@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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