partclone.xfs: free(): invalid next size (normal)
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Could you try partclone partclone 0.2.81? Thomas fixed a related issue about TUI.
Due to the upload issue on Sourceforge, we are not able to upload it. However, you can find that on:
http://free.nchc.org.tw/drbl-core/pool/drbl/unstable/partclone/
Steven.
Can I together with Clonezilla Alternative-testing (Wily), just do 'dpkg -i partclone_0.2.81-drbl1_amd64.deb' or is drbl needed?
Yes, you can.
Please let us know the results.
Thanks.
Steven.
It is cloning right now, but it looks bad. I can see a pattern: Every time it has been failing, it has been taking a long time to clone the empty space. Now it has been working close to 30 minutes with the empty space and it will have to work at 1.5 hours more to finish.
Partclone is claiming all the time that 0s are left until ready but still it takes hours to finish.
Then when 100% is reached after a long time, it crashes.
I will report more when the clone is finished, but I am almost sure this one too will fail.
So could you please try to enter the expert mode of Clonezilla live, and choose "-nogui" option:
http://clonezilla.org/clonezilla-live/doc/02_Restore_disk_image/advanced/09-advanced-param.php
By doing this, we can isolate the problem is on TUI or not.
Thank you very much.
Steven.
Both with and without -nogui the same crash happens right when the image is ready.
At this moment, the partition crashing the image creation is around 400Gb and empty but formated with XFS.
So how did you create the xfs partition? And on which GNU/Linux distribution? We need more info so that we could try to reproduce this issue here.
Thanks.
Steven.
Last edit: Steven Shiau 2015-07-31
I have tried to create the XFS partition with various tools: Ubuntu Trusty installer, gparted, fdisk.
When I created the partition manually (with fdisk) I formated it with 'mkfs.xfs /dev/sda3'.
Distros tested for creating the partition so far: Ubuntu Trusty and whatever Parted Magic 2013 is based upon.
When letting the installer take care of creating the partitions and formating it, it failed on /dev/sda1 (/). When manually creating the partitions either with gparted or with fdisk, it failed on /dev/sda3 (empty).
Last edit: engblom 2015-07-31
"When letting the installer take care of creating the partitions and formating it, it failed on /dev/sda1 (/). When manually creating the partitions either with gparted or with fdisk, it failed on /dev/sda3 (empty)." ->
What did you mean by this? Let me try to get the scenario. Did you mean you use Trusty amd64 CD to install the system and choosed xfs as the file system, after the system was installed, you used Clonezilla live 20150715-wily amd64 to save the image, and it failed to save the image on /dev/sda1?
BTW, could you please run:
parted -s /dev/sda print
and show me the results?
Thanks.
Steven.
Here comes the output from 'parted -s /dev/sda print'
Here comes the output from 'fdisk -lu'
The parted.out and the fdisk.out shows the scenario after I created the partitions again with gparted (which also formated them). Sda1 I populated with tar. Sda3 I never touched. Additionally I have chrooted into sda1 and been running 'grub-install /dev/sda' and updating the uuid in fstab. That is all.
I usually prefer to have the swap last on the disk, but the same problem appears regardless of the order of the partitions on the disk. I have two computers, one where sda2 is physically in the middle and then the one I created the parted.out where sda2 is physically at the end.
Could you please give Clonezilla live
20150731-wily
20150731-vivid
or
2.4.2-29
a try?
You can find them on
http://clonezilla.org/downloads.php
I have tested them on the fresh CentOS 7 x86-64 installation with xfs file system or Ubuntu trusty amd64 with xfs file system, too. They all work without any issue when saving the images.
Please let us know the results.
Thanks.
Steven.
I tried to create the image from two computers. Both crashed in the very same way: at 100% when the image of sda3 was made. Sda3 is the big empty XFS partition. There was no problem with sda1. It took 2 hours, 15 minutes to clone the empty partition.
Which iso/zip file did you use?
clonezilla-live-20150731-vivid-amd64.iso? Or?
Steven.
20150731-wily
amd64
Somehow I just could not reproduce the issue here. As I have mentioned, I tried to have a 500 GB disk, and have the similar xfs partition like yours, but the saving went well.
I also just did a test to save the new, empty xfs with 447 GB partition, and the saving was OK, not problem at all.
I am wondering maybe this is hardware issue there.
Do you have different machine you can try? Or please do a memtest to see if RAM is OK or not.
Steven.
I have difficulties to believe I have faulty RAM in all three computers. I have one Dell Latitude 3330 and two Dell Latitude 3340. They have about the same hardware (Intel I3). This time I only tried it from the two 3340s, but earlier when I tested, I also used the 3330. All three computers are from separate orders and the 3330 was bought more than a year before the 3340.
I will try to take out the hard disk and clone through an USB adapter from another computer.
The strange thing is that this all worked one year ago when I had a similar project with XFS and made images.
No idea at all. I can not reproduce the problem here, so I do not know how to ask Thomas Tsai to fix it. Besides, so far you are the only one reported this, that makes me wonder if the issue is on hardware. However, from your description, apparently looks like it's not.
If the older version of Clonezilla live works for you, then please keep using the old version. That's the only solution I think for the moment.
Steven.
I have tested from a HP ProBook 4340s through an USB-adapter. I still got the very same result. It is crashing at 100%.
For some reason I can not get older versions to work either. It looks like my only option is to use dd.
Last edit: engblom 2015-08-04
I just downloaded the latest Clonezilla, 2.4.2-32 which has Partclone v 0.2.81, and attempted to clone a 1TB drive. On that drive is a 980GB XFS partition with 5.2GB used. All went well until the process reached the XFS partition. The Elapsed Time and Time Remaining operated as expected for the 5.2GB of data, with Remaining Time reaching zero as the 5.2GB was processed, but then the cloning continued into the empty part of the partition and would have required several hours to finish. The total blocks indicated 239246592. Obviously Clonezilla is not ignoring the blank space.
This is still broken when it comes to XFS partitions.
This is exactly my situation. It takes many, many hours to clone the empty space and upon finishing the empty space of the partition, it crashes.