Trying to copy 1.9 TB data from a raw disk to a larger one of 2.6 TB and then, at some point, the transaction stops due lack of space on destination disk. Did a research on that and found that this has to do with the difference in block size of source (512) and destination (4096) disks. Then I've looked for solutions to create a disk with block size of 512, without success. Could anyone point out some direction where to look for?
Any help would be highly appreciated!
(Some detail that I've missed out earlier and could be helpful)
There is a file called data.dd which I've mounted using loop mounting.
root@server:# fdisk -l data.dd Disk data.dd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type data.dd1 1 3907024064 3907024064 1.8T fd Linux raid autodetect root@server:# losetup /dev/loop1 data.dd -o $((1 * 512)) root@server:# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop1 7:1 0 1.8T 0 loop └─shark-storage 252:25 0 1.7T 0 lvm root@server:# mount /dev/shark/storage /storage/mnt/ root@server:# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/shark-storage 1.7T 1.5T 193G 89% /storage/mnt
Finally, I am copying it's data to another disk either by using cp or rsync. Neither of them are completing.