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.
On Wednesday 10 November 2004 16:02, Jan Derfinak wrote:
> On Wed, 10 Nov 2004, Nathan Scott wrote:
> > On Tue, Nov 09, 2004 at 05:36:47PM -0500, Melissa Terwilliger wrote:
> > > I have a dual opteron SuSE 9 SLES machine running 2.6.9 kernel. The
> > I guess that means you built your own kernel (since SLES9 is a
> > 2.6.5 based kernel). Did you enable CONFIG_LBD?
> 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-XFS CVS-2004-10-22_05:00_UTC with ACLs, large block/inode numbers, no
> debug enabled
> > > I can create the partitions using parted & when I mount the two
> > > partitions they show up correctly as 2.6 TB each and they seem to be
> > > working perfectly. When I reboot the system I get the error:
> > > kernel:XFS:size check 2 failed in the kernel log and the mount command
> > > came back bad superblock on /dev/sdb1. I can no longer mount the
> Is there possibility that parted changes only kernel idea about partition
> table but not real disk layout? Did you try fdisk?