Sparse files

From Kicksecure
Revision as of 16:52, 19 September 2023 by Patrick (talk | contribs) (Text replacement - "\{\{(\w+)\s(\w+)\s(\w+)\}\}" to "{{$1_$2_$3}}")
Jump to navigation Jump to search

On Sparse Files, checking their real size versus their apparent size.

Introduction

Kicksecure KVM images are sparse files. In result, on common Linux operating systems with common file systems such as ext4 these appear to be taking 100 GB of disk space but in reality only use ~ 1 GB disk space time of writing. Different utilities show the apparent size versus the actual size.

Wikipedia notes: [1]

In computer science, a sparse file is a type of computer file that attempts to use file system space more efficiently when the file itself is partially empty. This is achieved by writing brief information (metadata) representing the empty blocks to disk instead of the actual "empty" space which makes up the block, using less disk space. The full block size is written to disk as the actual size only when the block contains "real" (non-empty) data. When reading sparse files, the file system transparently converts metadata representing empty blocks into "real" blocks filled with null bytes at runtime. The application is unaware of this conversion.

Check Real Size

You must change directory into the correct folder first. For your home folder. Depending on which one you want to check.

Click = Copy Copied to clipboard! cd ~

Or.

Click = Copy Copied to clipboard! cd /var/lib/libvirt/images/

Run.

Click = Copy Copied to clipboard! du -h Kicksecure-*.qcow2

Should show something like this.

2.5G Kicksecure-*.qcow2

Check Apparent Size

Run.

Click = Copy Copied to clipboard! du -h --apparent-size Kicksecure-*.qcow2

Should show something like this.

101G Kicksecure-*.qcow2

Also See

Maybe interesting:

Footnotes

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!