From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Is there a "make hole" (truncate in middle) syscall?
Date: Sat, 06 Dec 2003 00:25:56 +0100 [thread overview]
Message-ID: <yw1xad663kzf.fsf@kth.se> (raw)
In-Reply-To: 20031205224142.GR29119@mis-mike-wstn.matchmail.com
Mike Fedyk <mfedyk@matchmail.com> writes:
>> I found this paragraph in the man page of GNU cp:
>>
>> --sparse=WHEN
>> always Always make the output file sparse. This is
>> useful when the input file resides on a
>> filesystem that does not support sparse
>> files, but the output file is on a filesys-
>> tem that does.
>
> So with this, you can create sparse files for an entire set of files
> by just cping them? :)
Yes. It won't query the system for where any potential holes in the
source files might be, though, so if there are large holes, cp will
spend unnecessary time crunching through them.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2003-12-05 23:26 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 20:32 Is there a "make hole" (truncate in middle) syscall? Rob Landley
2003-12-04 20:55 ` Måns Rullgård
2003-12-04 21:10 ` Szakacsits Szabolcs
2003-12-05 0:02 ` Rob Landley
2003-12-04 22:33 ` Szakacsits Szabolcs
2003-12-05 11:22 ` Helge Hafting
2003-12-05 12:11 ` Måns Rullgård
2003-12-05 22:41 ` Mike Fedyk
2003-12-05 23:25 ` Måns Rullgård [this message]
2003-12-05 23:33 ` Szakacsits Szabolcs
2003-12-05 23:25 ` Szakacsits Szabolcs
2003-12-04 21:48 ` Mike Fedyk
2003-12-04 23:59 ` Rob Landley
2003-12-05 22:42 ` Olaf Titz
2003-12-04 22:53 ` Peter Chubb
2003-12-05 1:04 ` Philippe Troin
2003-12-05 2:39 ` Peter Chubb
2003-12-08 4:03 ` bill davidsen
2003-12-04 23:23 ` Andy Isaacson
2003-12-04 23:42 ` Szakacsits Szabolcs
2003-12-05 2:03 ` Mike Fedyk
2003-12-05 7:09 ` Ville Herva
2003-12-05 11:22 ` Anton Altaparmakov
2003-12-05 11:44 ` viro
2003-12-05 14:27 ` Anton Altaparmakov
2003-12-05 21:00 ` sparse file performance (was Re: Is there a "make hole" (truncate in middle) syscall?) Andy Isaacson
2003-12-05 21:12 ` Linus Torvalds
2003-12-08 20:43 ` Andy Isaacson
2003-12-11 5:13 ` Is there a "make hole" (truncate in middle) syscall? Hua Zhong
2003-12-11 6:19 ` Rob Landley
2003-12-11 18:58 ` Andy Isaacson
2003-12-11 19:15 ` Hua Zhong
2003-12-11 19:43 ` Andreas Dilger
2003-12-12 21:37 ` Daniel Phillips
2003-12-11 19:48 ` Jörn Engel
2003-12-11 19:55 ` Hua Zhong
2003-12-11 19:58 ` Andy Isaacson
2003-12-12 12:18 ` Jörn Engel
2003-12-12 15:40 ` Andy Isaacson
2003-12-12 16:03 ` Jörn Engel
2003-12-11 20:32 ` Rob Landley
2003-12-12 12:55 ` Jörn Engel
2003-12-12 13:28 ` Vladimir Saveliev
2003-12-12 13:43 ` Jörn Engel
2003-12-12 13:52 ` Vladimir Saveliev
2003-12-12 14:04 ` Jörn Engel
2003-12-12 13:53 ` Rob Landley
2003-12-12 14:01 ` Vladimir Saveliev
2003-12-12 21:35 ` Rob Landley
2003-12-15 10:00 ` Vladimir Saveliev
2003-12-15 11:52 ` Rob Landley
2003-12-15 13:26 ` Jörn Engel
2003-12-12 13:39 ` Rob Landley
2003-12-12 13:56 ` Jörn Engel
2003-12-12 14:24 ` Jörn Engel
2003-12-12 21:37 ` Rob Landley
2003-12-15 12:47 ` Jörn Engel
2003-12-16 5:43 ` Rob Landley
2003-12-16 11:05 ` Jörn Engel
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=yw1xad663kzf.fsf@kth.se \
--to=mru@kth.se \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).