[PVE-User] Backup size

Gilles Mocellin gilles.mocellin at nuagelibre.org
Fri Apr 4 18:30:37 CEST 2014


Le 04/04/2014 18:12, VIDAL, Thomas (Bioversity-France) a écrit :
> I will try Diaolin solution with zero.file.
> I will let you know on monday.
>
> Thanks in all the cases
>
> Thomas

For information, the package zerofree handle that case better than 
filing the whole filesystem with a file.

# LANG=C aptitude show zerofree
Package: zerofree
New: yes
State: not installed
Version: 1.0.2-1
Priority: extra
Section: admin
Maintainer: Thibaut Paumard <paumard at users.sourceforge.net>
Architecture: amd64
Uncompressed Size: 14.3 k
Depends: e2fslibs (>= 1.37), libc6 (>= 2.3.4)
Description: zero free blocks from ext2, ext3 and ext4 file-systems
  Zerofree finds the unallocated blocks with non-zero value content in 
an ext2, ext3 or ext4 file-system and fills them with zeroes (zerofree 
can also work with another value
  than zero). This is mostly useful if the device on which this 
file-system resides is a disk image. In this case, depending on the type 
of disk image, a secondary utility may
  be able to reduce the size of the disk image after zerofree has been 
run. Zerofree requires the file-system to be unmounted or mounted 
read-only.

  The usual way to achieve the same result (zeroing the unused blocks) 
is to run "dd" do create a file full of zeroes that takes up the entire 
free space on the drive, and then
  delete this file. This has many disadvantages, which zerofree alleviates:
  * it is slow;
  * it makes the disk image (temporarily) grow to its maximal extent;
  * it (temporarily) uses all free space on the disk, so other 
concurrent write actions may fail.

  Zerofree has been written to be run from GNU/Linux systems installed 
as guest OSes inside a virtual machine. If this is not your case, you 
almost certainly don't need this
  package. (One other use case would be to erase sensitive data a little 
bit more securely than with a simple "rm").
Homepage: http://intgat.tigress.co.uk/rmy/uml/index.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pve.proxmox.com/pipermail/pve-user/attachments/20140404/9147ed91/attachment-0015.html>


More information about the pve-user mailing list