From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: XFS Preallocate using ALLOCSP
Date: Wed, 17 Jun 2009 03:04:02 +0200 [thread overview]
Message-ID: <200906170304.02775@zmi.at> (raw)
In-Reply-To: <8770d98c0906161438u339440cdm783340485a3db898@mail.gmail.com>
On Dienstag 16 Juni 2009 Smit Shah wrote:
> In the vmware sparse disk
Ah, virtualization again. Yes, that's no good for performance ;-)
There's a "defragment disk" button in VMware which simply copies the
flat file on the filesystem in order to remove fragmentation. I guess
running xfs_fsr would help more in that case. Did you try with that?
> chunks are allocated of the size of 64k,
It's a pity that there's no option to define how large each chunk should
be. Using 1-50MB of real disk space for each new chunk could help a lot
to keep the file less fragmented. It get's really funny when you run
"defrag" within the VM on a sparse vdisk.
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-17 1:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 0:18 XFS Preallocate using ALLOCSP Smit Shah
2009-06-16 2:00 ` Smit Shah
2009-06-16 3:34 ` Eric Sandeen
2009-06-16 6:44 ` Smit Shah
2009-06-16 7:34 ` Smit Shah
2009-06-16 15:16 ` Eric Sandeen
2009-06-16 16:42 ` Felix Blyakher
2009-06-16 17:28 ` Smit Shah
2009-06-16 17:32 ` Eric Sandeen
2009-06-16 21:38 ` Smit Shah
2009-06-17 1:04 ` Michael Monnerie [this message]
2009-06-16 17:41 ` Felix Blyakher
2009-06-16 21:42 ` Smit Shah
2009-06-16 22:05 ` Eric Sandeen
2009-06-16 22:32 ` Felix Blyakher
2009-06-16 22:19 ` Smit Shah
2009-06-16 22:26 ` Felix Blyakher
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=200906170304.02775@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