From: Nicholas Miell <nmiell@comcast.net>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Jim Dennis <jimd@starshine.org>, linux-kernel@vger.kernel.org
Subject: Re: SEEK_HOLE and SEEK_DATA support?
Date: Fri, 03 Mar 2006 14:03:28 -0800 [thread overview]
Message-ID: <1141423408.2996.9.camel@entropy> (raw)
In-Reply-To: <44088360.2030705@cfl.rr.com>
On Fri, 2006-03-03 at 12:56 -0500, Phillip Susi wrote:
> Aren't there already apis to query for the holes in the file,
Yes, but they are filesystem-specific. (I think only XFS has them at
this point.)
> and doesn't tar already use them to efficiently back up sparse files?
No (at least, not in GNU tar 1.15.1).
--
Nicholas Miell <nmiell@comcast.net>
next prev parent reply other threads:[~2006-03-03 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 17:04 SEEK_HOLE and SEEK_DATA support? Jim Dennis
2006-03-03 17:56 ` Phillip Susi
2006-03-03 22:03 ` Nicholas Miell [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-02 21:49 Jim Dennis
2006-03-03 8:33 ` Lee Revell
2006-03-03 9:15 ` Arjan van de Ven
2006-03-05 3:05 ` Andrew Morton
2006-03-05 4:18 ` Nicholas Miell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1141423408.2996.9.camel@entropy \
--to=nmiell@comcast.net \
--cc=jimd@starshine.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox