I have a dual opteron SuSE 9 SLES machine running 2.6.9 kernel. The machine has 2 3ware 9500-12 PCI-X SATA raid cards installed with 12 250 GB drives on each card. I can create the partitions using p
I too had problems related to this configuration. In my case I was using a 12-channel 3Ware 9500 series controller along with 12 WD 250GB drives. XFS has been my default FS for some time now. Also,
I guess that means you built your own kernel (since SLES9 is a 2.6.5 based kernel). Did you enable CONFIG_LBD? XFS does a check on mount to make sure that the last sector on the device is actually ac
Hello. I'm curious, why there is CONFIG_LBD on 64-bit architecture? Is there because of VFS issue? I'm using Athlon64 kernel with CONFIG_LBD unset and XFS seems to use large block/inode numbers: SGI-
Are you sure config_lbd is unset? Everyone of my Opteron and Athlon64 machines have this set. I run SLES9 on everything, including my laptop. This seems to be the default setting. -Mike
It is default setting on SLES9 but I use self compiled kernel. I don't have disks bigger than 2TB, I had unset it. 2.6.9 #2 Mon Nov 8 02:07:41 CET 2004 x86_64 SGI-XFS CVS-2004-10-22_05:00_UTC with AC
zcat /proc/config.gz | grep CONFIG_LBD So I do have that set. Should I have that unset do you think? I have not used fdisk because I was told that it would work properly on disks over 2TB, the 3ware
I'm guessing there's a problem with parted somewhere.... you might use fdisk to print the partition headers and see if it looks ok - if not, I guess either fdisk or parted has a problem. I suppose th
... Thanks. I asked because I think that CONFIG_LBD isn't necessary on x86_64 platform but I was not sure. Other 64-bit archs work without it. It looks for me like an inaccurancy in kernel config. ja
I think that there is no difference on 64-bit system. You can leave it on. I propose to use original SLES9 kernel if it is possible. It is well tested and approved by many companies. Simplest thing y
I have a dual opteron SuSE 9 SLES machine running 2.6.9 kernel. The machine has 2 3ware 9500-12 PCI-X SATA raid cards installed with 12 250 GB drives on each card. I can create the partitions using p
I too had problems related to this configuration. In my case I was using a 12-channel 3Ware 9500 series controller along with 12 WD 250GB drives. XFS has been my default FS for some time now. Also,
I guess that means you built your own kernel (since SLES9 is a 2.6.5 based kernel). Did you enable CONFIG_LBD? XFS does a check on mount to make sure that the last sector on the device is actually ac
Hello. I'm curious, why there is CONFIG_LBD on 64-bit architecture? Is there because of VFS issue? I'm using Athlon64 kernel with CONFIG_LBD unset and XFS seems to use large block/inode numbers: SGI-
Are you sure config_lbd is unset? Everyone of my Opteron and Athlon64 machines have this set. I run SLES9 on everything, including my laptop. This seems to be the default setting. -Mike
It is default setting on SLES9 but I use self compiled kernel. I don't have disks bigger than 2TB, I had unset it. 2.6.9 #2 Mon Nov 8 02:07:41 CET 2004 x86_64 SGI-XFS CVS-2004-10-22_05:00_UTC with AC
zcat /proc/config.gz | grep CONFIG_LBD So I do have that set. Should I have that unset do you think? I have not used fdisk because I was told that it would work properly on disks over 2TB, the 3ware
I'm guessing there's a problem with parted somewhere.... you might use fdisk to print the partition headers and see if it looks ok - if not, I guess either fdisk or parted has a problem. I suppose th
... Thanks. I asked because I think that CONFIG_LBD isn't necessary on x86_64 platform but I was not sure. Other 64-bit archs work without it. It looks for me like an inaccurancy in kernel config. ja
I think that there is no difference on 64-bit system. You can leave it on. I propose to use original SLES9 kernel if it is possible. It is well tested and approved by many companies. Simplest thing y