Re: > 2TB storage

Re: > 2TB storage

[Randy.Dunlap]

On Mon, 24 Oct 2005, Carlos Pardo wrote:

> To everyone,
>
> Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
> essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset. It reported around 300 Megabytes
> instead of the expected 2200 Megabytes. How is the disk geometry determined ? Is it done by
> reading the IDENTIFY data or by accessing the BIOS ? Thanks in advance for any feedback.

With CONFIG_LBD enabled or disabled?

Please post precise log messages.

-- 
~Randy

> 2TB storage

[Carlos Pardo]

To everyone,

Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset. It reported around 300 Megabytes
instead of the expected 2200 Megabytes. How is the disk geometry determined ? Is it done by 
reading the IDENTIFY data or by accessing the BIOS ? Thanks in advance for any feedback.  

C Pardo

Re: > 2TB storage

[Jeff Garzik]

Carlos Pardo wrote:
> To everyone,
> 
> Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
> essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset. It reported around 300 Megabytes
> instead of the expected 2200 Megabytes. How is the disk geometry determined ? Is it done by 
> reading the IDENTIFY data or by accessing the BIOS ? Thanks in advance for any feedback.  

We read IDENTIFY DEVICE data directly, and use that...

Make sure you have CONFIG_LBD turned on, as Randy mentioned.  There may 
be other factors at play here too that I'm not seeing...

	Jeff

Re: > 2TB storage

[Randy.Dunlap]

On Mon, 24 Oct 2005, Jeff Garzik wrote:

> Carlos Pardo wrote:
> > To everyone,
> >
> > Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
> > essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset. It reported around 300 Megabytes
> > instead of the expected 2200 Megabytes. How is the disk geometry determined ? Is it done by
> > reading the IDENTIFY data or by accessing the BIOS ? Thanks in advance for any feedback.
>
> We read IDENTIFY DEVICE data directly, and use that...
>
> Make sure you have CONFIG_LBD turned on, as Randy mentioned.  There may
> be other factors at play here too that I'm not seeing...

With CONFIG_LBD=n and drive size near max 32-bit value,
there is a drive size calculation overflow error.
That's (another) reason that I asked for precise message logs.

It only affects the reported size (in the message log).
James has a fix for it.

-- 
~Randy

RE: > 2TB storage

[Carlos Pardo]

Randy,

I did not get any errors. Will recheck CONFIG_LBD settings. This is what I saw:

With open source driver: 

scsi1: sata_sil
SCSI device sda: 586153984 512-byte hdwr sectors (300111 MB)
SCSI device sda: drive cache: write back
mke2fs reports => 2232 

With our driver:

sda : use 0xffffffff as device size
SCSI device sda: 4294967296 512-byte hdwr sectors (2199023 MB)
SCSI device sda: drive cache: none
mke2fs reports => 16384

C-

-----Original Message-----
From: Randy.Dunlap [mailto:rdunlap@xenotime.net]
Sent: Monday, October 24, 2005 8:54 AM
To: Jeff Garzik
Cc: Carlos Pardo; Tejun Heo; linux-ide@vger.kernel.org; Edward Falk
Subject: Re: > 2TB storage


On Mon, 24 Oct 2005, Jeff Garzik wrote:

> Carlos Pardo wrote:
> > To everyone,
> >
> > Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
> > essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset. It reported around 300 Megabytes
> > instead of the expected 2200 Megabytes. How is the disk geometry determined ? Is it done by
> > reading the IDENTIFY data or by accessing the BIOS ? Thanks in advance for any feedback.
>
> We read IDENTIFY DEVICE data directly, and use that...
>
> Make sure you have CONFIG_LBD turned on, as Randy mentioned.  There may
> be other factors at play here too that I'm not seeing...

With CONFIG_LBD=n and drive size near max 32-bit value,
there is a drive size calculation overflow error.
That's (another) reason that I asked for precise message logs.

It only affects the reported size (in the message log).
James has a fix for it.

-- 
~Randy

RE: > 2TB storage

[Randy.Dunlap]

On Mon, 24 Oct 2005, Carlos Pardo wrote:

> Randy,
>
> I did not get any errors. Will recheck CONFIG_LBD settings. This is what I saw:
>
> With open source driver:
>
> scsi1: sata_sil
> SCSI device sda: 586153984 512-byte hdwr sectors (300111 MB)
> SCSI device sda: drive cache: write back
> mke2fs reports => 2232
>
> With our driver:
>
> sda : use 0xffffffff as device size

Wasn't there a message above this one?  There should have been
one like:

		printk(KERN_NOTICE "%s : READ CAPACITY(16) failed.\n"
		       "%s : status=%x, message=%02x, host=%d, driver=%02x \n",

> SCSI device sda: 4294967296 512-byte hdwr sectors (2199023 MB)
           == hex: 1_0000_0000

Looks to me like you really need CONFIG_LBD=y.

What CPU arch. are you using?

> SCSI device sda: drive cache: none
> mke2fs reports => 16384
>
> C-
>
> -----Original Message-----
> From: Randy.Dunlap [mailto:rdunlap@xenotime.net]
> Sent: Monday, October 24, 2005 8:54 AM
> To: Jeff Garzik
> Cc: Carlos Pardo; Tejun Heo; linux-ide@vger.kernel.org; Edward Falk
> Subject: Re: > 2TB storage
>
>
> On Mon, 24 Oct 2005, Jeff Garzik wrote:
>
> > Carlos Pardo wrote:
> > > To everyone,
> > >
> > > Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
> > > essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset. It reported around 300 Megabytes
> > > instead of the expected 2200 Megabytes. How is the disk geometry determined ? Is it done by
> > > reading the IDENTIFY data or by accessing the BIOS ? Thanks in advance for any feedback.
> >
> > We read IDENTIFY DEVICE data directly, and use that...
> >
> > Make sure you have CONFIG_LBD turned on, as Randy mentioned.  There may
> > be other factors at play here too that I'm not seeing...
>
> With CONFIG_LBD=n and drive size near max 32-bit value,
> there is a drive size calculation overflow error.
> That's (another) reason that I asked for precise message logs.
>
> It only affects the reported size (in the message log).
> James has a fix for it.

-- 
~Randy

Re: > 2TB storage

[Bryan O'Sullivan]

On Mon, 2005-10-24 at 08:35 -0700, Carlos Pardo wrote:

> Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
> essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset.

Since you appear work for SiImage, was this a SteelVine SV-2000 box?
That ships configured as a port multiplier, not a fake RAID.  There are
no Linux drivers that can usefully talk to it, and no software available
for Linux to reconfigure it out of JBOD mode.  It's a Windows-only box.

	<b

RE: > 2TB storage

[Carlos Pardo]

You are correct. It is actually an SV-2000 configured as "BIG". It concatenates the disk drives to make them look like one gigantic disk. There will soon be a way to configure the SV-2000 under Linux.

C- 

-----Original Message-----
From: Bryan O'Sullivan [mailto:bos@serpentine.com]
Sent: Monday, October 24, 2005 9:43 AM
To: Carlos Pardo
Cc: Jeff Garzik; Tejun Heo; linux-ide@vger.kernel.org; Edward Falk
Subject: Re: > 2TB storage


On Mon, 2005-10-24 at 08:35 -0700, Carlos Pardo wrote:

> Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
> essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset.

Since you appear work for SiImage, was this a SteelVine SV-2000 box?
That ships configured as a port multiplier, not a fake RAID.  There are
no Linux drivers that can usefully talk to it, and no software available
for Linux to reconfigure it out of JBOD mode.  It's a Windows-only box.

	<b

RE: > 2TB storage

[Carlos Pardo]

Randy et al,

I will retest and do a more accurate report in a couple of days. Thanks.

C-

-----Original Message-----
From: Randy.Dunlap [mailto:rdunlap@xenotime.net]
Sent: Monday, October 24, 2005 9:20 AM
To: Carlos Pardo
Cc: Randy.Dunlap; Jeff Garzik; Tejun Heo; linux-ide@vger.kernel.org;
Edward Falk
Subject: RE: > 2TB storage


On Mon, 24 Oct 2005, Carlos Pardo wrote:

> Randy,
>
> I did not get any errors. Will recheck CONFIG_LBD settings. This is what I saw:
>
> With open source driver:
>
> scsi1: sata_sil
> SCSI device sda: 586153984 512-byte hdwr sectors (300111 MB)
> SCSI device sda: drive cache: write back
> mke2fs reports => 2232
>
> With our driver:
>
> sda : use 0xffffffff as device size

Wasn't there a message above this one?  There should have been
one like:

		printk(KERN_NOTICE "%s : READ CAPACITY(16) failed.\n"
		       "%s : status=%x, message=%02x, host=%d, driver=%02x \n",

> SCSI device sda: 4294967296 512-byte hdwr sectors (2199023 MB)
           == hex: 1_0000_0000

Looks to me like you really need CONFIG_LBD=y.

What CPU arch. are you using?

> SCSI device sda: drive cache: none
> mke2fs reports => 16384
>
> C-
>
> -----Original Message-----
> From: Randy.Dunlap [mailto:rdunlap@xenotime.net]
> Sent: Monday, October 24, 2005 8:54 AM
> To: Jeff Garzik
> Cc: Carlos Pardo; Tejun Heo; linux-ide@vger.kernel.org; Edward Falk
> Subject: Re: > 2TB storage
>
>
> On Mon, 24 Oct 2005, Jeff Garzik wrote:
>
> > Carlos Pardo wrote:
> > > To everyone,
> > >
> > > Has anyone tested libATA drivers using disks bigger than 2 Terabytes? I just attached what is
> > > essentially a 2.2 TB disk drive to a Silicon Image 3114 chipset. It reported around 300 Megabytes
> > > instead of the expected 2200 Megabytes. How is the disk geometry determined ? Is it done by
> > > reading the IDENTIFY data or by accessing the BIOS ? Thanks in advance for any feedback.
> >
> > We read IDENTIFY DEVICE data directly, and use that...
> >
> > Make sure you have CONFIG_LBD turned on, as Randy mentioned.  There may
> > be other factors at play here too that I'm not seeing...
>
> With CONFIG_LBD=n and drive size near max 32-bit value,
> there is a drive size calculation overflow error.
> That's (another) reason that I asked for precise message logs.
>
> It only affects the reported size (in the message log).
> James has a fix for it.

-- 
~Randy