Bernard Michaud

Thank you. I hadn’t seen a mention of the partclone version in the changelog for the alternative testing version 20260315. The changelog for partclone 0.3.47 lists the following updates: 2026-03-10 Thomas Tsai <tlinux.tsai@gmail.com> update github action for debian build Merge pull request #290 from Thomas-Tsai/xfs-update Xfs update Merge pull request #291 from Thomas-Tsai/add-debian-ci Add debian ci add dependence package liburcu-dev for xfs It is therefore obvious it was essentially released to...

Hi Steven, I recently upgraded from clonezilla-live-20251017-questing-amd64 with partclone 0.3.38 to clonezilla-live-20260220-questing-amd64 with partclone 0.3.45 (I only use stable versions unless absolutely necessary). However, my first backups of xfs-based Linux systems, namely Debian 13 (Trixie) and Rocky Linux 10.1 caused a large number of warning messages to fill the screen. This is an example for the root logical volume of Debian 13: # partclone.xfs -c -s /dev/mapper/debianvg-lv01 -o debianvg-lv01.img...

Hi Steven, I recently upgraded from clonezilla-live-20251017-questing-amd64 with partclone 0.3.38 to clonezilla-live-20260220-questing-amd64 with partclone 0.3.45 (I only use stable versions unless absolutely necessary). However, my first backups of xfs-based Linux systems, namely Debian 13 (Trixie) and Rocky Linux 10.1 caused a large number of warning messages to fill the screen. This is an example for the root logical volume of Debian 13: # partclone.xfs -c -s /dev/mapper/debianvg-lv01 -o debianvg-lv01.img...

Hi Steven, I recently upgraded from clonezilla-live-20251017-questing-amd64 with partclone 0.3.38 to clonezilla-live-20260220-questing-amd64 with partclone 0.3.45 (I only use stable versions unless absolutely necessary). However, my first backups of xfs-based Linux systems, namely Debian 13 (Trixie) and Rocky Linux 10.1 caused a large number of warning messages to fill the screen. This is an example for the root logical volume of Debian 13: # partclone.xfs -c -s /dev/mapper/debianvg-lv01 -o debianvg-lv01.img...

Hi Steven, I recently upgraded from clonezilla-live-20251017-questing-amd64 with partclone 0.3.38 to clonezilla-live-20260220-questing-amd64 with partclone 0.3.45 (I only use stable versions unless absolutely necessary). However, my first backups of xfs-based Linux systems, namely Debian 13 (Trixie) and Rocky Linux 10.1 caused a large number of warning messages to fill the screen. This is an example for the root logical volume of Debian 13: # partclone.xfs -c -s /dev/mapper/debianvg-lv01 -o debianvg-lv01.img...

I gave the new test release 20220118-impish a try. Beforehand, I edited /boot/grub/grub.cfg and added parameters use_dev_list_cache=no and use_os_prober=no to my customary boot entries. I can report that performance is well within the realm of 20210817-hirsute, my reference release. So, all things considered, I am satisfied that I can continue to use Clonezilla on this machine by disabling the dev list cache. As well, I appreciate the parameter to disable os_prober; the workaround was not overly...

Well, it’s not all bad; at least I now know to specify the use_dev_list_cache=no parameter in Clonezilla releases 20220109-impish and beyond and get back the same processing speed I had before. I guess it beats standing still and continue to use release 20210817-hirsute, which works fine on my machine but will no longer evolve.

The same thing happened to me a few weeks ago. I think the culprit is partclone. I have a few btrfs filesystems, not system partitions as I don’t quite trust it enough yet to install entire Linux distributions using btrfs (it is still technically in development, and is not considered entirely stable by many). One of those btrfs filesystems is used as a repository and is 300 GB in size. I have been backing it up with Clonezilla for over two years until suddenly it failed, no reason given. I installed...