I usually back up my main 256GB btrfs disk to a 3TB btrfs RAID 1 array but
with version three it is predicting 3 hrs plus instead of the usual 30-40
mins?!?
Not sure if it's the Linux kernel has some regressions about your hardware. Could you please give Ubuntu-based Clonezilla live, i.e., 20220522-jammy a try: https://clonezilla.org/downloads.php
It comes with different Linux kernel so the results might be different.
Steven
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the same symptoms.
I am a Windows 11 user.
Backups are going slow.
I chose a fast backup.
But I'm doing a slow backup
I'm using the program very well.
Thank you.
Hope the bug is fixed.
3.0.0-25-amd64 test live
Last edit: krdondon 2022-06-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As previous post. Please give testing Clonezilla live 3.0.1-2 and 20220531-* a try: https://clonezilla.org/downloads.php
and let's know the results.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also noticed issues as it takes a lot longer to finish...
-clonezilla-live-3.0.0-26-amd64.iso = about 1.60GB/min (which is slow as previous "clonezilla-live-2.8.1-12-amd64.iso" worked as expected, which is in the general 7.00GB/min range give or take)
-clonezilla-live-20220522-jammy-amd64.iso = about 7.00GB/min (which is expected)
which ads a lot of time to imaging. but it appears the next version should fix this issue given what's said above.
p.s. I use a i5-3550 CPU and basically a 2TB Hitachi hard drive imaging my boot drive (SSD) to a image file on that 2TB hard drive and I was using my usual option near the bottom of the list, but I forgot what it's called. but it's in relation to the zstd I think, the one that uses multi-cores.
Last edit: ThaCrip 2022-06-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We made some improvement about using "-z9p" to save the image.
It can be even more faster then it was in Clonezilla live 2.8.1-12
If you can, please give testing Clonezilla live a try, i.e., 3.0.1-5 or 20220606-* and use the option "-z9p" to save the image: https://clonezilla.org/downloads.php
Please let us know the results.
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech (I had the basic board since March 2006) as it's a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a image file on a 80GB IDE hard drive and, in short, the new version is a bit faster as you can see results below...
-clonezilla-live-3.0.0-26-amd64.iso = about 530-535MB/min early into the test (which I imagine would have further slowed down had it let it finish the entire imaging process). but I stopped it with CTRL+C since it will take too long to finish.
-clonezilla-live-3.0.1-5-amd64.iso (testing) = about 2.65GB/min high, 1.72GB/min low. total time... 9min0sec @ 1.78GB/min.
so as you can see the new testing version is about 1 minute faster than the previously good working version on this particular computer.
p.s. I know I used the "-z9p" because I always select what I think is 'expert' mode and select what I usually select and then that "-z9p" (I made sure to look for this just to confirm it's using that specifically) and then proceed to image the hard drive to a image file on another hard drive etc. basically I always use the "-z9p" option when using Clonezilla for general imaging.
👍
1
Last edit: ThaCrip 2022-06-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great. Apparently it's faster.
Here for my testing laptop (about 3-year old, i7 CPU with 16 GB RAM) with SSD, save the image to NFS server. I can see the transferring rate is about 10 GB/min for Clonezilla live 3.0.1-5, while it's about 7-8 GB/min IIRC for Clonezilla live 2.8.1-12.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it broke the network cloning, remote destination throws a "read error: No such file or directory" when zstd is selected. No error given when I switch to gz.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was able to replicate this again.
command ran was
ocs-onthefly -np netcat --net-filter zstd -sfsck -k0 -p choose -a -f nvme0n1
the issue was with NTFS partition with win10 on nvme0n1p4
it will throw a read ERROR: No such file or directory
If I were to use the latest 3.0.2-6 it will throw a read image_hdr error=0
problem went away if using bzip2 or gzip as compression
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This kind of weird issue normally is related to hardware. As we can not reproduce this issue here. We tried on different hardware, at 3 types, and all works well for Clonezilla live 3.0.1-5 with -z9p.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I finally got around to using 'clonezilla-live-3.0.1-7-amd64.iso' on my primary PC with the i5-3550 CPU and on my boot SSD (Samsung 850 EVO 250GB) to a image file on a 2TB hard drive and it did 9.63GB/min average (at it's peak during the imaging process it was a bit over 10GB/min). previously with that same general setup it was about 7.00GB/min, possibly a bit less in the mid-to-high 6's.
Last edit: ThaCrip 2022-06-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your feedback. Yes, without using "--rsyncable" with zstd, it's much faster. In my test machine, saving the disk image to a NFS image repository, the rate is about 15 GB/min.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I usually back up my main 256GB btrfs disk to a 3TB btrfs RAID 1 array but
with version three it is predicting 3 hrs plus instead of the usual 30-40
mins?!?
Not sure if it's the Linux kernel has some regressions about your hardware. Could you please give Ubuntu-based Clonezilla live, i.e., 20220522-jammy a try:
https://clonezilla.org/downloads.php
It comes with different Linux kernel so the results might be different.
Steven
OK. Thx. I just trying older version, but will test jammy in future.
Last edit: Lee Seymour 2022-05-29
Yes, as you suspected Jammy & previous stable working as intended. Thx!
OK, thanks for your feedback.
Is this issue reproducible on all of your machines? Or just some specific type of machines?
Thanks.
Steven
Yes, my ancient C2D setup & reproducible on my fairly modern ThinkPad X250.
Got it. Could you please show the green command you used, as shown here:
https://clonezilla.org/clonezilla-live/doc/01_Save_disk_image/images/ocs-10-8-img-save-command-prompt.png
BTW, which repository did you save to? network storage? USB external disk? Or?
Thanks.
Steven
/usr/sbin/ocs-sr -q2 -c -j2 -z9p -i 0 -sfsck -scs -senc -p poweroff savedisk
I tend to use identical command structure on all my machines. It went wrong with both internal disk & external USB 3.0 disk.
Thanks for providing more info about this issue.
We found actually this issue is due to the zstd's performance regression:
https://github.com/facebook/zstd/issues/2966
https://github.com/zalando/nakadi/pull/1407
Hence we downgraded zstd to 1.4.8 in the testing Clonezilla live. Please give Clonezilla live 3.0.1-2 and 20220531-* a try:
https://clonezilla.org/downloads.php
Steven
I have the same symptoms.
I am a Windows 11 user.
Backups are going slow.
I chose a fast backup.
But I'm doing a slow backup
I'm using the program very well.
Thank you.
Hope the bug is fixed.
3.0.0-25-amd64 test live
Last edit: krdondon 2022-06-01
As previous post. Please give testing Clonezilla live 3.0.1-2 and 20220531-* a try:
https://clonezilla.org/downloads.php
and let's know the results.
Thanks.
Steven
Thank you. I just checked It works well. It got faster.
Cheetah. Delivery. :)
OK, great. Thanks for your feedback.
We will report this issue to the upstream, i.e., zstd.
Steven
I also noticed issues as it takes a lot longer to finish...
-clonezilla-live-3.0.0-26-amd64.iso = about 1.60GB/min (which is slow as previous "clonezilla-live-2.8.1-12-amd64.iso" worked as expected, which is in the general 7.00GB/min range give or take)
-clonezilla-live-20220522-jammy-amd64.iso = about 7.00GB/min (which is expected)
which ads a lot of time to imaging. but it appears the next version should fix this issue given what's said above.
p.s. I use a i5-3550 CPU and basically a 2TB Hitachi hard drive imaging my boot drive (SSD) to a image file on that 2TB hard drive and I was using my usual option near the bottom of the list, but I forgot what it's called. but it's in relation to the zstd I think, the one that uses multi-cores.
Last edit: ThaCrip 2022-06-06
We made some improvement about using "-z9p" to save the image.
It can be even more faster then it was in Clonezilla live 2.8.1-12
If you can, please give testing Clonezilla live a try, i.e., 3.0.1-5 or 20220606-* and use the option "-z9p" to save the image:
https://clonezilla.org/downloads.php
Please let us know the results.
Ref: https://github.com/facebook/zstd/issues/3150
Steven
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech (I had the basic board since March 2006) as it's a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a image file on a 80GB IDE hard drive and, in short, the new version is a bit faster as you can see results below...
-clonezilla-live-2.8.1-12-amd64.iso = about... 2.25GB/min high, 1.58GB/min low. total time... 9min58sec @ 1.61GB/min.
-clonezilla-live-3.0.0-26-amd64.iso = about 530-535MB/min early into the test (which I imagine would have further slowed down had it let it finish the entire imaging process). but I stopped it with CTRL+C since it will take too long to finish.
-clonezilla-live-3.0.1-5-amd64.iso (testing) = about 2.65GB/min high, 1.72GB/min low. total time... 9min0sec @ 1.78GB/min.
so as you can see the new testing version is about 1 minute faster than the previously good working version on this particular computer.
p.s. I know I used the "-z9p" because I always select what I think is 'expert' mode and select what I usually select and then that "-z9p" (I made sure to look for this just to confirm it's using that specifically) and then proceed to image the hard drive to a image file on another hard drive etc. basically I always use the "-z9p" option when using Clonezilla for general imaging.
Last edit: ThaCrip 2022-06-08
Great. Apparently it's faster.
Here for my testing laptop (about 3-year old, i7 CPU with 16 GB RAM) with SSD, save the image to NFS server. I can see the transferring rate is about 10 GB/min for Clonezilla live 3.0.1-5, while it's about 7-8 GB/min IIRC for Clonezilla live 2.8.1-12.
Steven
I think it broke the network cloning, remote destination throws a "read error: No such file or directory" when zstd is selected. No error given when I switch to gz.
NTFS partition only. EXT3 and FAT32 are okay
I was able to replicate this again.
command ran was
ocs-onthefly -np netcat --net-filter zstd -sfsck -k0 -p choose -a -f nvme0n1
the issue was with NTFS partition with win10 on nvme0n1p4
it will throw a read ERROR: No such file or directory
If I were to use the latest 3.0.2-6 it will throw a read image_hdr error=0
problem went away if using bzip2 or gzip as compression
Switch to 522 jammy version and still same problem when zstd was selected as compression for network cloning. gzip is okay.
The fault went away, can't replicate it again.
This kind of weird issue normally is related to hardware. As we can not reproduce this issue here. We tried on different hardware, at 3 types, and all works well for Clonezilla live 3.0.1-5 with -z9p.
Steven
I finally got around to using 'clonezilla-live-3.0.1-7-amd64.iso' on my primary PC with the i5-3550 CPU and on my boot SSD (Samsung 850 EVO 250GB) to a image file on a 2TB hard drive and it did 9.63GB/min average (at it's peak during the imaging process it was a bit over 10GB/min). previously with that same general setup it was about 7.00GB/min, possibly a bit less in the mid-to-high 6's.
Last edit: ThaCrip 2022-06-22
Thanks for your feedback. Yes, without using "--rsyncable" with zstd, it's much faster. In my test machine, saving the disk image to a NFS image repository, the rate is about 15 GB/min.
Steven