My ext4 disk crashed and I'm using ddrescue to try to rescue it. However the crashed disk is 3tb, and I only have another 3tb drive for the image file. I assumed that this image file will be too big for the brand new empty disk, so after 2700gb had been rescued I interrupted the process to try to write the rest of the image to a second disk.
I started the process with
ddrescue -v --no-split /dev/sdc /mnt/red/imagefile /mnt/500gb/logfile
/dev/sdc is the crashed disk /mnt/red is the new hard disk, imagefile is my image /mnt/500gb/logfile is the logfile
Everything looked normal until I interrupted the imaging, so I attempted to continue the image on the second disk using:
ddrescue -v --no-split /dev/sdc /mnt/500gb/imagefile2 /mnt/500gb/logfile
ie, exactly the same command as before, only directing the image file to another disk
However, after just a few seconds ddrescue quits and complains that there is no space left on the device, but the device is empty apart from the logfile. What I don't understand is that imagefile2 is created immediately with a size of 2,732,050,104,320 (assume bytes), which is roughly the same size as the amount rescued in the first image file.
I cannot find any instructions anywhere as to why this might be. I assumed the second image file would be roughly the same size as the remaining amount to be rescued. ie 250gb.