Implement SCSI READ(16), WRITE(16) and SAI READ CAPACITY(16) commands, so SCSI disks larger than 2TB can work with guests that support these newer SCSI commands. I have tested the attached patch with a RHEL 5 full virt guest, by creating, fscking and mounting a 3TB ext3 filesystem, as well as by running Stephen Tweedie's verify-data program from both dom0 and the guest.
Created attachment 330188 [details] patch that adds support for >2TB SCSI disks
I have submitted the equivalent patch upstream.
Fix built into xen-3.0.3-83.el5
My system is ext3 file system, and I add the file in the: /var/lib/xen/images, when I add 2TB file it is ok, but add 3TB file, it is said the file is too large.
Which part of the system is telling you the file is too big? virt-manager? xend? something else? Also, are you on a 32 or 64 bit system?
I first try to create a image file by using: dd if=/dev/zero of=example.img bs=4096 count=1 seek=500M (This is for 2TB file and this is ok) And using: ll example.img -h I will see the file is 2TB Using this way, I try to create 3TB, then the system just report that : dd:truncating at 3221225472000 bytes in output file 'example.img': File too large. I do not know this error message belongs to which part. And both 32 and 64 bit system can get the same results.
2TB is the maximum ext2/ext3 file size limit. You will have to use a sparse LVM volume to test this. Comment #29 in bug #479339 shows how to do this.
Verified on xen-3.0.3-91.el5
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1328.html