bin/71408: bsdlabel refuses to label a 2.7TB array on a 3ware 9500-12 SATA controller

[Nick Evans]

The following reply was made to PR bin/71408; it has been noted by GNATS.

From: Nick Evans <nevans at talkpoint.com>
To: "'freebsd-gnats-submit at FreeBSD.org'" <freebsd-gnats-submit at FreeBSD.org>
Cc:  
Subject: Re: bin/71408: bsdlabel refuses to label a 2.7TB array on a 3ware
	 9500-12 SATA controller
Date: Wed, 8 Sep 2004 11:14:59 -0400 

 Recreated an array with total size 1.81TB:
 
 da0 at twa0 bus 0 target 0 lun 0
 da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device
 da0: 100.000MB/s transfers
 da0: 1907264MB (3906076672 512 byte sectors: 255H 63S/T 243142C)
 
 karmacoma# bsdlabel -w da0 auto
 karmacoma# bsdlabel da0  
 # /dev/da0:
 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   a: 3906076656       16    unused        0     0       
   c: 3906076672        0    unused        0     0         # "raw" part,
 don't edit
 
 bsdlabel behaves fine.
 
 Recreated with total size ~2.2TB
 
 da0 at twa0 bus 0 target 0 lun 0
 da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device 
 da0: 100.000MB/s transfers
 da0: 2384080MB (4882595840 512 byte sectors: 255H 63S/T 303927C)
 
 karmacoma# bsdlabel -w da0 auto
 karmacoma# bsdlabel da0  
 # /dev/da0:
 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   a: 587628528       16    unused        0     0
   c: 587628544        0    unused        0     0         # "raw" part, don't
 edit
 
 bsdlabel creates a 280gig partition...
 
 It seems that 2 terabytes is the treshold when bsdlabel starts acting funny.