What I cloned:
Linux 3.16.2 with Btrfs-Progs version 3.16
Cloning:
btrfs check & Scrubbed /dev/sda3 - No errors.
Full disk Image of /dev/sda made with Clonezilla Live vers.: 2.2.3-25
SHA1 hash, check img after cloning
No problems whatsoever.
Restore:
Check SHA1 of Disk image - OK
Restore /dev/sda3 - OK [Tried both running and disabling the auto-resize, no difference]
No problems whatsoever.
Result:
Kernel panic. BTRFS detects checksum mismatches and it refuses to mount.
Btrfs check | Shows no errors at all.
Btrfs scrub detects 4672 mismatches. 4672 corrupted files.
Filesystem was fine before cloning, Clonezilla reported absolutely no issues during the cloning itself or the disk image check. Fine and dandy during restore but ending with a devastated btrfs partition.
I don't know what I did wrong, but I know at least two seperate people got bitten like this.
Out of the all the data loss I expected to happen with btrfs during use, it happened because I wanted to restore the MBR in a hurry.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the bug report. Btrfs is still under development in Linux kernel, so it might change.
Yes, we should keep updating that. I will urge the developer of Partclone to update that.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What I cloned:
Linux 3.16.2 with Btrfs-Progs version 3.16
Cloning:
btrfs check & Scrubbed /dev/sda3 - No errors.
Full disk Image of /dev/sda made with Clonezilla Live vers.: 2.2.3-25
SHA1 hash, check img after cloning
No problems whatsoever.
Restore:
Check SHA1 of Disk image - OK
Restore /dev/sda3 - OK
[Tried both running and disabling the auto-resize, no difference]
No problems whatsoever.
Result:
Kernel panic. BTRFS detects checksum mismatches and it refuses to mount.
Btrfs check | Shows no errors at all.
Btrfs scrub detects 4672 mismatches. 4672 corrupted files.
Filesystem was fine before cloning, Clonezilla reported absolutely no issues during the cloning itself or the disk image check. Fine and dandy during restore but ending with a devastated btrfs partition.
I don't know what I did wrong, but I know at least two seperate people got bitten like this.
Out of the all the data loss I expected to happen with btrfs during use, it happened because I wanted to restore the MBR in a hurry.
Thanks for the bug report. Btrfs is still under development in Linux kernel, so it might change.
Yes, we should keep updating that. I will urge the developer of Partclone to update that.
Steven.