From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Wipe patch
Date: Wed, 2 Aug 2006 04:49:21 +0200 [thread overview]
Message-ID: <fb249edb0608011949o366fca15m113b1c73af25dbb7@mail.gmail.com> (raw)
In-Reply-To: <44D00D26.2050201@wasp.net.au>
On 02/08/06, Brad Campbell <brad@wasp.net.au> wrote:
> ZIGLIO, Frediano, VF-IT wrote:
> > Hi,
> > well, this is not a definitive patch but it works. The aim is to be
> > able to wipe the disk without allocating entire space. When you wipe a
> > disk the program fill disk with zero bytes so disk image increase to
> > allocate all space. This just patch detect null byte writes and do not
> > write all zero byte clusters.
> >
>
> I've been giving this some pretty heavy testing over the last week and can say I've not noticed any
> negative performance impact or any other adverse side effects, not to mention the speedup when doing
> re-packing (which I do fairly regularly on both ext3 and ntfs guest filesystems).
>
> While I'm here does anyone know of a simple program, either dos or linux based for wiping unused
> space on fat filesystems? The only ones I've found so far have been windows based.
I don't know if you mean just zeroing unused parts or reordering the
data and stuff like defragmentation. If you mean the former, there's a
universal method:
dd if=/dev/zero of=xxx; rm xxx
where xxx is a path to a new file on the filesystem, which must be
mounted. It will creata a zero filled file there, which will fill all
availiable space, and remove the file afterwards. I used this when I
needed to send filesystem images through internet so that they
compressed well.
If you add dd=<a-big-number-here> it might take less time to write the file.
>
> This patch now conflicts pretty heavily with the new AIO changes it would seem. Further
> investigation required.
>
> Ta,
> Brad
> --
> "Human beings, who are almost unique in having the ability
> to learn from the experience of others, are also remarkable
> for their apparent disinclination to do so." -- Douglas Adams
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
Regards,
--
balrog 2oo6
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
next prev parent reply other threads:[~2006-08-02 2:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 8:23 [Qemu-devel] Wipe patch ZIGLIO, Frediano, VF-IT
2006-07-26 8:41 ` Brad Campbell
2006-07-26 9:19 ` Avi Kivity
2006-07-26 9:35 ` Brad Campbell
2006-08-02 2:25 ` Brad Campbell
2006-08-02 2:49 ` andrzej zaborowski [this message]
2006-08-02 2:51 ` andrzej zaborowski
2006-08-02 3:09 ` Brad Campbell
2006-08-02 7:39 ` Nigel Horne
2006-08-02 17:32 ` Andreas Bollhalder
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 8:48 ZIGLIO, Frediano, VF-IT
2006-07-26 9:42 ZIGLIO, Frediano, VF-IT
2006-07-26 9:52 ` Brad Campbell
2006-08-02 12:53 ZIGLIO, Frediano, VF-IT
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=fb249edb0608011949o366fca15m113b1c73af25dbb7@mail.gmail.com \
--to=balrog@zabor.org \
--cc=balrogg@gmail.com \
--cc=qemu-devel@nongnu.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).