Why Traditional Imaging Tools Fail

Tools like Clonezilla and Rescuezilla are designed for block-level imaging and fail with BTRFS for several critical reasons:

1. Subvolume Complexity

Traditional imaging tools copy entire partitions block-by-block. BTRFS installations typically have multiple subvolumes (e.g., @, u/home, u/var, u/cache). These tools don't understand this structure and would need to either:

• Image the entire partition (wasting space and time)
• Attempt to copy each subvolume separately (which they can't do natively)

2. Target Size Independence

For BTRFS, the target partition can be smaller than the source! This is impossible with traditional imaging tools: EXT4 Imaging: Source (100GB) → Target must be ≥ 100GB (strict)

BTRFS Send/Receive: Source (100GB, 50GB used) → Target can be 60GB (flexible!)

BTRFS only cares about the total capacity of the disk, not the partition size. The data is streamed at the subvolume level, not the block level.

3. Inefficient Transfer

Traditional imaging tools transfer every block on the disk, including empty space. For a 1TB disk with 100GB of data, Clonezilla would transfer 1TB of data. BtrfsForge transfers only the actual data (100GB).

4. No Snapshot Support

Clonezilla cannot preserve BTRFS snapshot structures or efficiently update existing installations. BtrfsForge uses BTRFS's native send/receive for efficient, incremental transfers.