xfs
[Top] [All Lists]

Re: XFS Preallocate using ALLOCSP

To: xfs@xxxxxxxxxxx
Subject: Re: XFS Preallocate using ALLOCSP
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 17 Jun 2009 03:04:02 +0200
In-reply-to: <8770d98c0906161438u339440cdm783340485a3db898@xxxxxxxxxxxxxx>
Organization: it-management http://it-management.at
References: <24042506.post@xxxxxxxxxxxxxxx> <4A37D737.70004@xxxxxxxxxxx> <8770d98c0906161438u339440cdm783340485a3db898@xxxxxxxxxxxxxx>
User-agent: KMail/1.10.3 (Linux/2.6.30-ZMI; KDE/4.1.3; x86_64; ; )
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

<Prev in Thread] Current Thread [Next in Thread>