| To: | Carsten Oberscheid <oberscheid@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Strange fragmentation in nearly empty filesystem |
| From: | Felix Blyakher <felixb@xxxxxxx> |
| Date: | Tue, 27 Jan 2009 09:41:25 -0600 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20090127143724.GP16931@xxxxxxxxxxxx> |
| References: | <20090123102130.GB8012@xxxxxxxxxxxx> <20090124003329.GE32390@disturbed> <20090126075724.GA1753@xxxxxxxxxxxx> <497E02CD.2020000@xxxxxxxxxxx> <20090127071023.GA16511@xxxxxxxxxxxx> <20090127084034.GA16931@xxxxxxxxxxxx> <497F0C78.7060501@xxxxxxxxxxx> <20090127143724.GP16931@xxxxxxxxxxxx> |
On Jan 27, 2009, at 8:37 AM, Carsten Oberscheid wrote: Just out of couriosity (and stubbornness): Are there any XFS parameters that might influence fragmentation for the better, in case I have to put up with a stupid application? Not much could be tuned in XFS for random writes over the holes. Ideally such file should be preallocated. Can you provide vmware the zero filled file by doing dd if=/dev/zero of=foo.mem count=512 bs=1024k instead of letting vmware populate it over the time and thus badly fragmenting it. Felix |
| Previous by Date: | Re: Strange fragmentation in nearly empty filesystem, Carsten Oberscheid |
|---|---|
| Next by Date: | Re: [PATCH 10/17] xfs: factor out attr fork reset handling, Felix Blyakher |
| Previous by Thread: | Re: Strange fragmentation in nearly empty filesystem, Carsten Oberscheid |
| Next by Thread: | Re: Strange fragmentation in nearly empty filesystem, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |