24

I've learned from this article to use sdelete as a step to shrink VDI file:

sdelete -c c:

But what does the -c ('Clean free space' as described by its help text) mean? Doesn't it write free space with zero? And what about -z(Zero free space)? What is the different between sdelete -c and -z?

Edit

I tried the step in the article mentioned before, but failed to reduce the size of the .vid file. Then I followed this superuser post, and changed the option -c to -z, and succeeded.

So it seems -z writes zeros to free space, and -c writes something else (random bits possibly).

21

I think this is a common mistake. Maybe the -z option was not available in earlier versions. SDelete 1.61 says

-z         Zero free space (good for virtual disk optimization)

Note that doing so will first expand your hard disk to the full size. Only in the shrinking process by VMWare it will become smaller again.

A quick test on my machine:

-z took 1:01 minutes
-c took 2:11 minutes

Which indicates that -z only writes simple zeros whereas -c is the military standard wiping DoD 5220.22-M as written on the SDelete website.

  • It won’t bloat the file if the software is somewhat intelligent. Most virtualization applications are. I just tried it in VMware Fusion, it did not increase the file size at all. – Daniel B May 1 '14 at 13:11
  • 1
    VMWare Workstation Pro 12 does expand the disk to full size, unfortunately. – Lebenita Aug 27 '15 at 23:59
  • -c and -z were advertised in 1.51 exactly the other way around (whether that was just an error in the description or the functions were also reversed I don't know). The 1.61 way makes a lot more sense, obviously. – Lebenita Aug 28 '15 at 0:01
  • Just checked with Windows 2012 and a new 20GB VHDX file. The -z option was very fast (seconds) and the VHDX disk file didn't increase in size. The -c option is running much slower and the VHDX is increasing in size. So -z is the preferred option for a so-called thin/expanding virtual hard disk especially if you've over committed disk space. But it's not as safe as the -c option – munrobasher Dec 10 '15 at 14:07
  • 1
    Just checked the latest version (2.0) and there are two obvious differences. Firstly there is a 32-bit and 64-bit version (sdelete.exe & sdelete64.exe). But there is also a subtle difference in the -c command which worries. In v1.61, the -c option said "Cleaning free space" but in v2.0 it says "Zeroing free space". The -z option also says zeroing. Has it lost the random data option?? – munrobasher Jan 17 '17 at 17:38
5

This should have been more appropriately posted as a comment to Thomas' answer, but since I cannot do that yet, I post it here.

Mixing up the "-z" and "-c" options is probably a "common mistake", because SDelete has changed the behavior of said options over the years. Looking at the below provided references it seems that SDelete first had a "-z" option which did the "military standard wiping", then added a "-c" option for zeroing free space, and then somewhere between v1.51 and v1.61 switched that behavior to the current one.

References: sysinternals.com Forum and old SDelete homepage on Microsoft TechNet via archive.org.

  • This is not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. – DavidPostill Dec 3 '14 at 16:45
  • 4
    This is not an answer to the original question. Please reread the first line of the post though. If there is a better procedure for adding useful and/or pertinent information to an already existing answer for someone, who just signed up to the service, feel free to enlighten me. – LN2 Dec 6 '14 at 20:37
  • "If there is a better procedure for adding useful and/or pertinent information to an already existing answer for someone, who just signed up to the service, feel free to enlighten me" - there isn't, please read the links I provided. – DavidPostill Dec 6 '14 at 21:43
  • It's interesting to note in 1.61 regardless of which switch you use it always says "Zeroing free space" (and in 1.51 it always says "Cleaning free space"). That's a bit misleading, for a while it made me distrust that "-c" was actually "clean" and not "zero" behavior. – rkagerer Jul 30 '16 at 22:55
5

Current documentation (and program version 2.01):

  • -c: Clean free space. Specify an option amount of space to leave free for use by a running system.
  • -z: Zero free space (good for virtual disk optimization).

But in older versions it was reversed:

  • -c: Zero free space (good for virtual disk optimization).
  • -z: Clean free space.

enter image description here

But what do they do?

Clean creates the largest file it can, and fills it with random data, and then fills it with zeros. This is what most people think of as wiping, and it's overkill.

The downside is that if you are using a virtual disk, or inside a virtual machine, or running it on a storage space: the underlying storage system will be forced to allocate resources to hold you random data, and then hold zero. Hopefully then the underlying storage system will realize that all that space that was just allocated to your drive can be reclaimed because all those sectors simply contain zeros.

-z Zero: Simply writes zeros to all sectors. This is the option you want, for many reasons:

  • wiping with random data is overkill (reading data is not practically possible; i.e. one bit at a time though a microscope is not feasable)
  • some SSDs can detect that you are writing zero to a sector, and can use that to mark the sector as free (similar to a TRIM)
  • most virtual storage systems (VMWare, Hyper-V, Windows Virtual Disks, Storage Spaces) realize that you are writing an entire sector of zeros, and take the opportunity to reclaim space in the underlying storage file
  • SSDs won't know that your ultimate goal is essentially a glorified TRIM, and (like the virtual disks) be forced to fill sectors that already contained zeros, with non-zeros, only to have you fill it with zeros again. That's terrible for your SSDs.

Source: Mounted a virtual hard disk, and watched the I/O operations that sdelete took in both modes.

tl;dr: Use -z Zero. It's faster, better, safer.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.