From: Daniel Phillips <phillips@bonn-fries.net>
To: "Ph. Marek" <marek@bmlv.gv.at>,
"Dr. Michael Weller" <eowmob@exp-math.uni-essen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: sparse file creation in existing data?
Date: Fri, 29 Jun 2001 17:03:41 +0200 [thread overview]
Message-ID: <0106291703410C.00419@starship> (raw)
In-Reply-To: <3.0.6.32.20010629133915.0091e470@pop3.bmlv.gv.at> <3.0.6.32.20010629145529.00922ae0@pop3.bmlv.gv.at>
In-Reply-To: <3.0.6.32.20010629145529.00922ae0@pop3.bmlv.gv.at>
On Friday 29 June 2001 14:55, Ph. Marek wrote:
> Hmmm, on second thought ... But I'd like it better to have a fcntl for
> hole-making :-)
> Maybe I'll implement this myself.
A far superior interface would be:
ssize_t sys_clear(unsigned int fd, size_t count)
A stub implementation would just write zeroes. You would need a generic way
of determining whether holes are supported for a particular file - this is
where an fcntl would be appropriate. It would also be nice to know this
before opening/creating a file, perhaps by fcntling the directory.
But don't expect to have a real, hole-creating implementation any time soon.
Taming the truncate races is hard enough as it is with a single boundary at
the end of a file. Taking care of multiple boundaries inside the file is
far, far harder. Talk to Al Viro or the Ext3 team if you want the whole ugly
story.
--
Daniel
next prev parent reply other threads:[~2001-06-29 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.A32.3.95.1010629135834.61212E-100000@werner.exp-math. uni-essen.de>
2001-06-29 11:39 ` Ph. Marek
2001-06-29 12:20 ` Dr. Michael Weller
2001-06-29 12:55 ` Ph. Marek
2001-06-29 15:03 ` Daniel Phillips [this message]
2001-06-29 18:38 ` Andreas Dilger
2001-06-30 11:33 ` Pavel Machek
2001-07-09 6:43 ` Andreas Dilger
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=0106291703410C.00419@starship \
--to=phillips@bonn-fries.net \
--cc=eowmob@exp-math.uni-essen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marek@bmlv.gv.at \
/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
all inboxes | Powered by JetHome®