Hello, without using partitions it works. Thanks for the hint! The second problem I addressed is also solved. The large partitions defined with yast are valid only until the next reboot. Therefore exporting a >2TB partition to a DOMU resulted in destroing the partition. After rebooting of DOM0 the partition was gone in DOM0 too. So it is not a xen problem. Perhaps a yast error? Gustav Steffen Winterfeldt schrieb:
On Sat, 17 Mar 2007, Dr. Gustav Quade wrote:
for an advanced scientific project we use a large server with 64Gbyte memory and 10TB disk space. Since some jobs will run for several weeks we plan to use virtual machines which can be saved during maintenance tasks.
Using kernel 2.6.18.8-0.1-xen x86_64 I can create a several terabytes large partition using yast. Using xfs I created a 4.7 terabytes large file. df -k: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sde1 6835799424 4608001068 2227798356 68% /test
Fdisk, sfdisk or cfdisk show wrong partition size.
[...]
I have two questions:
1. why fdisk is not showing the correct partition date?
The classical PC (MS-DOS) partition table uses 32-bit block numbers. So you'll be in trouble with partitions >= 2TB. Nothing to be done about that.
You could go for a GPT scheme (at least parted can do it 'mklabel gpt'). Or, as a simple workaround, don't use partitions.
Steffen --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org