| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Strange fragmentation in nearly empty filesystem |
| From: | Carsten Oberscheid <oberscheid@xxxxxxxxxxxx> |
| Date: | Tue, 27 Jan 2009 15:39:26 +0100 |
| In-reply-to: | <200901271030.43234@xxxxxx> |
| References: | <20090123102130.GB8012@xxxxxxxxxxxx> <20090127071023.GA16511@xxxxxxxxxxxx> <20090127084034.GA16931@xxxxxxxxxxxx> <200901271030.43234@xxxxxx> |
| User-agent: | Mutt/1.5.13 (2006-08-11) |
On Tue, Jan 27, 2009 at 10:30:38AM +0100, Michael Monnerie wrote: > What if you dd if=foo.vmem of=test bs=1000 ? That would do nearly the > same as your "create empty file" test. [co@tangchai]~/vmware/foo dd if=foo.vmem of=test_dd bs=1000 536870+1 Datensätze ein 536870+1 Datensätze aus 536870912 Bytes (537 MB) kopiert, 3,76026 s, 143 MB/s [co@tangchai]~/vmware/foo xfs_bmap -vvp test_dd | grep hole | wc -l0 [co@tangchai]~/vmware/foo xfs_bmap -vvp test_dd | grep -v hole | wc -l 10 Looks good. Seems like I'm ready to accept that XFS is innocent. See other post. Thank you & best regards Carsten Oberscheid |
| Previous by Date: | Re: xfs open questions, Eric Sandeen |
|---|---|
| Next by Date: | Re: Strange fragmentation in nearly empty filesystem, Carsten Oberscheid |
| Previous by Thread: | Re: Strange fragmentation in nearly empty filesystem, Michael Monnerie |
| Next by Thread: | Re: Strange fragmentation in nearly empty filesystem, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |