public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: sparsify - utility to punch out blocks of 0s in a file
Date: Mon, 06 Feb 2012 03:44:43 +0400	[thread overview]
Message-ID: <4F2F146B.6050003@msgid.tls.msk.ru> (raw)
In-Reply-To: <4F2D90B6.4070008@redhat.com>

On 05.02.2012 00:10, Eric Sandeen wrote:
[]

Just a very quick look:

>  * sparsify - utility to punch out blocks of 0s in a file
> int main(int argc, char **argv)
> {
[]
> 	if (optind == argc) {
> 		printf("Error: no filename specified\n");
> 		usage();
> 	}
> 
> 	fname = argv[optind++];

There's no handling of the case when there are more than one file
specified on the command line.


> 	/*
> 	 * Normalize to blocksize-aligned range:
> 	 * round start down, round end up - get all blocks including the range specified
> 	 */
> 
> 	punch_range_start = round_down(punch_range_start, blocksize);
> 	punch_range_end = round_up(punch_range_end, blocksize);
> 	min_hole = round_up(min_hole, blocksize);
> 	if (!min_hole)
> 		min_hole = blocksize;

I think this deserves some bold warning if punch_range_start
or punch_hole_end is not a multiple of blocksize.

[]
> 	/*
> 	 * Read through the file, finding block-aligned regions of 0s.
> 	 * If the region is at least min_hole, punch it out.
> 	 * This should be starting at a block-aligned offset
> 	 */
> 
> 	while ((ret = read(fd, readbuf, min_hole)) > 0) {
> 
> 		if (!memcmp(readbuf, zerobuf, min_hole)) {

Now this is interesting.  Can ret be < min_hole?  Can a read
in a middle of a file be shorter than specified?

How it will work together with some other operation being done
at the same file -- ftruncate anyone?

Thanks!

/mjt

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2012-02-05 23:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 20:04 sparsify - utility to punch out blocks of 0s in a file Eric Sandeen
2012-02-04 20:10 ` Eric Sandeen
2012-02-04 20:17   ` Eric Sandeen
2012-02-05 15:05   ` Raghavendra D Prabhu
2012-02-05 23:44   ` Michael Tokarev [this message]
2012-02-05 23:55     ` Eric Sandeen
2012-02-05  9:33 ` Ron Yorston
2012-02-05 16:36   ` Eric Sandeen
2012-02-05 16:55     ` Andreas Dilger
2012-02-05 17:23       ` Matthias Schniedermeyer
2012-02-05 17:23       ` Eric Sandeen
2012-02-05 19:24         ` Andreas Dilger
2012-02-05 17:19     ` Ron Yorston
2012-02-05 17:21       ` Eric Sandeen
2012-02-06 18:40 ` Sunil Mushran
2012-02-06 21:41 ` Ted Ts'o
2012-02-06 21:47   ` Eric Sandeen

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=4F2F146B.6050003@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=xfs@oss.sgi.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