Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: 0.95-beta
Fetching contributors…

Cannot retrieve contributors at this time

121 lines (98 sloc) 5.041 kb
SquashFu - a combination of fun, squashfs, joy, happiness, aufs and rsync
REQUIREMENTS: bash, aufs, aufs2-util, squashfs-tools, rsync
SquashFu is currently beta quality. While there may be some undiscovered bugs,
the major components and structures in place will not change unless absolutely
necessary. This means that backups created today will still be useful 6 months
from now (if your config supports this).
Mini FAQ:
- Why not?
What currently works?
- Regular incrementals. Execute with sudo and the -B option
- Automatic merging incremenetals down to MIN_BINS once MAX_BINS has been exceeded
- Rolling back. Execute with sudo, the -R option, and a number of backups to roll back
- Reporting, executed with -Q, shows approx. disk usage and bin information
What's not yet included?
- A lot of error catching. While rsync takes care of itself and you'll suffer no
damage by aborting rsync in the middle of a backup, you could easily destroy
things by, for example, setting MIN_BINS greater than MAX_BINS.
What not to expect?
- Elephants
- Salvation
Goal: To create a backup solution which provides incremental backups and compression,
and which also provides an easy way to roll back.
A directory structure is created as follows (with some terminology included):
|- seed.sfs <-- squash, or seed
|- .bin.list <-- bin inventory list (or binventory)
|- ro/ <-- squash mount point
|- rw/ <-- union mount point
|- .bins/ <-- incrementals
| .....
| .....
| .....
| .....
| .....
seed.sfs is created from an initial backup and compressed using SquashFS, which is
simply a read only filesystem which focuses on compression. It's mounted, using a
loopback device, on ro/.
At the time of the backup, the next available bin is determined, created, and logged
to an inventory sheet with a timestamp. A union is created with all the available bins,
mounted in reverse chronological order on top of the seed (newest to oldest) on rw/.
At this point, the union represents the state of your files at the end of the last
backup. The newest branch is marked as read/write, and rsync is called. Because this
top branch is the only writable location in the union, the files rsync generates with
the -u (update) flag are placed into this branch. The backup finishes, and the union
and seed are unmounted.
At this point, Squashfu ensures compliance with the user's settings of MAX_BINS. If
the current number of used bins exceeds this value, a new seed is generated. The
number of old incrementals merged into the new seed is determined by the difference
between MAX_BINS and MIN_BINS in the config file. In this way, you always have
MIN_BINS available to roll back to, but you're not forced to recompress your seed
at every backup -- an operation that may take a long time depending on how big
your backup source is.
If and when you want to roll back, execute Squashfu with the -R action, and supply
the number of bins you want to roll back. The bins are ordered chronologically,
and the oldest "number_of_bins - bins_to_rollback" are mounted on the union mount
You should not, under any circumstances, add or remove files contained in the bins,
nor should you alter your binventory's time stamps. Doing so can result in non-recoverable
damage to the integrity of the backups.
Further reading:
INSTALL (if you're not on Arch Linux)
-Copy squashfu.conf as /etc/squashfu.conf
-Make a backup directory somewhere where you want your files
-READ OVER /etc/squashfu.conf and set it the way you want
-Run manually with 'squashfu -B'
-If everything goes well, make a cron job to run this bad boy at the time you want
-Hang onto ya nuts. As this is still an alpha, I take no responsibility for
loss of data, and I likely don't care much about bug reports.
1/11/2010 (Kernel:
Issue: Aufs takes a long time to unmount.
Fix: If using Ext4, mount with the 'nobarrier' option. No resolution known
at this time for other FS's.
Issue: Paths with special chars or whitespace as includes or excludes are
not properly handled when passed to rsync.
Fix: If you MUST be ridiculous, escape (not quote) the spaces and/or other
special characters.
In no particular order....
- Fix output funcs for non-color scenario
- Add semantic error checking for config
- Create man page
Jump to Line
Something went wrong with that request. Please try again.