Hello Plamen,
Converter does support large files (more than 4GB); currently it handles files up to 2TB. To be 100% sure I have explicitly tested a conversion of a 32bit RHEL 5.1 with a 5GB file in it.
---
I'm cloning a 64bit RHEL 5.8
Yes there are large files (2GB up) in this directory /srv/data203591
---
This is the first time I see such a complaint. I can only speculate about two possible reasons:
- a network error that has confused the 'untaring' (tar_1.20 is running on the destination VM)
- the tar on the source machine doesn't support larger than 4GB files (I don't really believe this is possible)
---
source has a tar version 1.15 (i don't think there is an issue with 1.15)
destination used tar 1.20
---
Have you tried the same conversion again?
---
Yes, I excluded the two big filesystems and the cloning was completed without error. However the SAN storage filesystems are missings and only the default OS filesystems are mounted in the cloned image.
I checked the 3 disks and all of them are present in the cloned image. What puzzled me was that the LVM (RHEL) is unable to detect the Physical disks, Volume Groups, and the Logical Volumes. When I tried to mount all the filesystems it says the special blocks associated to the above mount point /srv/data203591 /dev/<volume group> doesn't not exists.
---
I'm not sure if this is a bug or known issue to converter 5.1.