| To: | John Groves <John@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Question about sparse files |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Fri, 16 Jun 2006 10:23:06 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <4490B09F.20903@xxxxxxxxxxxxxx>; from John@xxxxxxxxxxxxxx on Wed, Jun 14, 2006 at 07:58:07PM -0500 |
| References: | <44905B9F.5000401@xxxxxxxxxxxxxx> <20060615081403.B918399@xxxxxxxxxxxxxxxxxxxxxxxx> <4490B09F.20903@xxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Wed, Jun 14, 2006 at 07:58:07PM -0500, John Groves wrote: > 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?) > > I presume that my hole must not just be a multiple of the filesystem > blocksize -- it should also be blocksize-aligned. A single-block chunk > that I lseek past while writing would be two sub-blocksize null sections > (but not a hole) unless it's blocksize-aligned. Right? Right. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Question about sparse files, Martin Steigerwald |
|---|---|
| Next by Date: | TAKE 952214 - fix logprint to handle 32/64bit inode/EFI format items, Timothy Shimmin |
| Previous by Thread: | Re: Question about sparse files, Martin Steigerwald |
| Next by Thread: | Re: Question about sparse files, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |