Update: The latest Koji scratch build is here
Symlinks on Windows filesystems are now displayed correctly. I’m not even going to begin explaining how this miracle was achieved, just look at the very complicated code.
#!/bin/sh - guestfish=fish/guestfish testimg=/mnt/tmp/test/test.img size=1G for fstype in ext2 ext3 ext4 xfs ntfs msdos ; do $guestfish <<EOF sparse $testimg $size run sfdiskM /dev/sda , mkfs $fstype /dev/sda1 EOF echo -n "$fstype: " du $testimg done
|Filesystem||Allocated kilobytes (out of 1G)||Overhead %|
|msdos & vfat||2076||0.2%|
|hfs & hfsplus ||16432||1.6%|
 Yes, there are shortcomings in the methodology. What this really measures is how many blocks are written by the mkfs program. Even if you believe the figures, this only measures the initial overhead, but you can use the same technique to measure the overhead of storing (eg) lots of small files, or whatever is appropriate for your workload.
 Note the difference between ext2 and ext3/4 seems to be entirely down to the size of the journal, which is a kind of metadata overhead, but one that you can easily control.
 Needs three small patches to libguestfs to get these filesystems to work.
 This seems off the scale — needs further investigation.
|akostadinov on Linux Kernel Library backend f…|
|Rory on What’s the maximum numbe…|
|Matthew Booth on Tip: Making a disk image …|
|Lars Kellogg-Stedman… on Tip: Ways to extract an ISO wi…|
|jhrcz on Be script friendly in your too…|
|Half-baked ideas: C… on OCaml internals part 2: String…|
|pozorvlak on Tip: Find the IP address of a…|
|SSD Caching –… on Using LVM’s new cache…|
|Ara on Using LVM’s new cache…|
|Eli on Tip: Making a disk image …|
I am Richard W.M. Jones, a computer programmer. I have strong opinions on how we write software, about Reason and the scientific method. Consequently I am an atheist [To nutcases: Please stop emailing me about this, I'm not interested in your views on it] By day I work for Red Hat on all things to do with virtualization.
My motto is "often wrong". I don't mind being wrong (I'm often wrong), and I don't mind changing my mind.
This blog is not affiliated or endorsed by Red Hat and all views are entirely my own.