[opensuse-factory] Large file size problem under xen
Hello, 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. yast: /dev/sde │ 6.3 TB│ │Areca-ARC-1280-VOL#04 /dev/sde1│ 6.3 TB│ │Linux native │/test fdisk -l /dev/sde Disk /dev/sde: 6999.9 GB, 6999999774720 bytes 255 heads, 63 sectors/track, 851034 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sde1 1 48986 393479629+ 83 Linux After "exporting" the disk to DomU the partition can't be mounted. mount /dev/hdc1 /test mount: /dev/hdc1: can't read superblock fdisk shows the same results as in Dom0 fdisk -l /dev/hdc Disk /dev/hdc: 6999.9 GB, 6999999774720 bytes 255 heads, 63 sectors/track, 851034 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 1 48986 393479629+ 83 Linux but yast in DomU is not able to recognize the correct partition size. /dev/hdc │ 6.3 TB│ │DISK hdc │ /dev/hdc1│ 375.2 GB│ │Linux native I have two questions: 1. why fdisk is not showing the correct partition date? 2. is xen forwarding the partition parameters correctly? Many thanks in advance Gustav Quade IMBIE Uni Bonn --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
"Dr. Gustav Quade" <quade@uni-bonn.de> writes:
Hello,
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.
yast: /dev/sde │ 6.3 TB│ │Areca-ARC-1280-VOL#04 /dev/sde1│ 6.3 TB│ │Linux native │/test
fdisk -l /dev/sde
Disk /dev/sde: 6999.9 GB, 6999999774720 bytes 255 heads, 63 sectors/track, 851034 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/sde1 1 48986 393479629+ 83 Linux
Please file a bug for this in bugzilla, fdisk should show the right data.
After "exporting" the disk to DomU the partition can't be mounted.
mount /dev/hdc1 /test mount: /dev/hdc1: can't read superblock
fdisk shows the same results as in Dom0
fdisk -l /dev/hdc
Disk /dev/hdc: 6999.9 GB, 6999999774720 bytes 255 heads, 63 sectors/track, 851034 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/hdc1 1 48986 393479629+ 83 Linux
but yast in DomU is not able to recognize the correct partition size.
/dev/hdc │ 6.3 TB│ │DISK hdc │ /dev/hdc1│ 375.2 GB│ │Linux native
I have two questions:
1. why fdisk is not showing the correct partition date? 2. is xen forwarding the partition parameters correctly?
Does it work if you are not using Xen? I mean: Can you create such a file with our default x86-64 kernel? Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
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
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
"Dr. Gustav Quade" <quade@uni-bonn.de> writes:
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?
Might be. Could you file a bugreport (see http://bugs.opensuse.org) and describe exactly how this can be reproduced? We should get this fixed for 10.3... thanks, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (3)
-
Andreas Jaeger -
Dr. Gustav Quade -
Steffen Winterfeldt