From: Eric Sandeen <sandeen@redhat.com>
To: Ron Yorston <rmy@tigress.co.uk>
Cc: xfs@oss.sgi.com, linux-ext4@vger.kernel.org
Subject: Re: sparsify - utility to punch out blocks of 0s in a file
Date: Sun, 05 Feb 2012 11:21:26 -0600 [thread overview]
Message-ID: <4F2EBA96.2070603@redhat.com> (raw)
In-Reply-To: <201202051719.q15HJJme010040@helium.internal.tigress.co.uk>
On 2/5/12 11:19 AM, Ron Yorston wrote:
> OK, I tried it out for my use case of flinging VM filesystem images around
> on ext4 and it seems to do the job. I don't have any 64-bit systems
> here at home so I used my feeble 32-bit netbook. Since sizeof(off_t) !=
> sizeof(long long) the debug output was all wrong:
>
> punching at 8989607068975104 len -4635819229210214401
whoops, I'll fix that thanks.
This is the problem when I start something as a hack and then expose it
to the light of day. ;)
-Eric
> but the image file and the host filesystem both survived the ordeal.
>
> Ron
WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@redhat.com>
To: Ron Yorston <rmy@tigress.co.uk>
Cc: linux-ext4@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: sparsify - utility to punch out blocks of 0s in a file
Date: Sun, 05 Feb 2012 11:21:26 -0600 [thread overview]
Message-ID: <4F2EBA96.2070603@redhat.com> (raw)
In-Reply-To: <201202051719.q15HJJme010040@helium.internal.tigress.co.uk>
On 2/5/12 11:19 AM, Ron Yorston wrote:
> OK, I tried it out for my use case of flinging VM filesystem images around
> on ext4 and it seems to do the job. I don't have any 64-bit systems
> here at home so I used my feeble 32-bit netbook. Since sizeof(off_t) !=
> sizeof(long long) the debug output was all wrong:
>
> punching at 8989607068975104 len -4635819229210214401
whoops, I'll fix that thanks.
This is the problem when I start something as a hack and then expose it
to the light of day. ;)
-Eric
> but the image file and the host filesystem both survived the ordeal.
>
> Ron
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-05 17:21 UTC|newest]
Thread overview: 34+ 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:04 ` Eric Sandeen
2012-02-04 20:10 ` Eric Sandeen
2012-02-04 20:10 ` Eric Sandeen
2012-02-04 20:17 ` Eric Sandeen
2012-02-04 20:17 ` Eric Sandeen
2012-02-05 15:05 ` Raghavendra D Prabhu
2012-02-05 15:05 ` Raghavendra D Prabhu
2012-02-05 23:44 ` Michael Tokarev
2012-02-05 23:44 ` Michael Tokarev
2012-02-05 23:55 ` Eric Sandeen
2012-02-05 23:55 ` Eric Sandeen
2012-02-05 9:33 ` Ron Yorston
2012-02-05 9:33 ` Ron Yorston
2012-02-05 16:36 ` Eric Sandeen
2012-02-05 16:36 ` Eric Sandeen
2012-02-05 16:55 ` Andreas Dilger
2012-02-05 16:55 ` Andreas Dilger
2012-02-05 17:23 ` Matthias Schniedermeyer
2012-02-05 17:23 ` Eric Sandeen
2012-02-05 17:23 ` Eric Sandeen
2012-02-05 19:24 ` Andreas Dilger
2012-02-05 19:24 ` Andreas Dilger
2012-02-05 17:19 ` Ron Yorston
2012-02-05 17:19 ` Ron Yorston
2012-02-05 17:21 ` Eric Sandeen [this message]
2012-02-05 17:21 ` Eric Sandeen
2012-02-06 18:40 ` Sunil Mushran
2012-02-06 18:40 ` [Ocfs2-devel] " Sunil Mushran
2012-02-06 18:40 ` Sunil Mushran
2012-02-06 21:41 ` Ted Ts'o
2012-02-06 21:41 ` Ted Ts'o
2012-02-06 21:47 ` Eric Sandeen
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=4F2EBA96.2070603@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rmy@tigress.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.