| To: | John Groves <John@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Question about sparse files |
| From: | Martin Steigerwald <Martin@xxxxxxxxxxxx> |
| Date: | Thu, 15 Jun 2006 09:44:36 +0200 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <4490B09F.20903@GrovesTech.com> |
| References: | <44905B9F.5000401@GrovesTech.com> <20060615081403.B918399@wobbly.melbourne.sgi.com> <4490B09F.20903@GrovesTech.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.9.1 |
Am Donnerstag 15 Juni 2006 02:58 schrieben Sie:
> Thanks Nathan and Eric. Roger to Eric's point re: holes smaller than
> the filesystem blocksize (I suppose I could lseek past a small chunk
> while writing, it just wouldn't be a hole, right?)
Hello John,
you can test yourself. xfs_bmap tells you about the holes in a file:
martin@deepdance:~/Amiga -> /usr/sbin/xfs_bmap Messages.hardfile
Messages.hardfile:
0: [0..18815]: 4650936..4669751
1: [18816..21527]: hole
2: [21528..100863]: 4672464..4751799
3: [100864..183039]: 11899536..11981711
4: [183040..651263]: 13764344..14232567
5: [651264..943615]: 16747816..17040167
6: [943616..1489407]: 18002488..18548279
7: [1489408..2097143]: hole
8: [2097144..2097151]: 18548280..18548287
Regards,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Question about sparse files, John Groves |
|---|---|
| Next by Date: | Re: Question about sparse files, Nathan Scott |
| Previous by Thread: | Re: Question about sparse files, John Groves |
| Next by Thread: | Re: Question about sparse files, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |