Port-amd64 archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Large disks with gpt on amd64
Dear list,
sorry, this maybe the wrong place to ask (I'm not sure if this is
port-specific), but let me try it here first:
I have several HP DL380G5 with MSA 60 RAID arrays attached and try to
use them under NetBSD. To be on the safe side, I tried the Jibbed live
distribution before installing.
The first results were promising, all relevant hardware was detected
with the shipped kernel, especially the logical devices on these RAID
arrays with ~10TB each:
# dmesg | grep ^sd
sd0 at scsibus0 target 0 lun 0: <HP, LOGICAL VOLUME, 5.26> disk fixed
sd0: 136 GB, 35132 cyl, 255 head, 32 sec, 512 bytes/sect x 286677120 sectors
sd1 at scsibus1 target 0 lun 0: <HP, LOGICAL VOLUME, 5.26> disk fixed
sd1: 9314 GB, 65535 cyl, 255 head, 1168 sec, 512 bytes/sect x
19534592432 sectors
sd1: mbr partition exceeds disk size
sd1: GPT GUID: 5de529bf-8519-4d58-a677-a195517f3159
sd2 at scsibus1 target 1 lun 0: <HP, LOGICAL VOLUME, 5.26> disk fixed
sd2: 9314 GB, 65535 cyl, 255 head, 1168 sec, 512 bytes/sect x
19534592432 sectors
sd2: GPT GUID: e53773a0-dffc-4fea-8afa-f6af15d77ef2
sd3 at scsibus1 target 2 lun 0: <HP, LOGICAL VOLUME, 5.26> disk fixed
sd3: 9314 GB, 65535 cyl, 255 head, 1168 sec, 512 bytes/sect x
19534592432 sectors
sd3: GPT GUID: 14019865-fbec-48a6-875a-e103510cba99
sd3: bad GPT partition array CRC
sd4 at scsibus1 target 3 lun 0: <HP, LOGICAL VOLUME, 5.26> disk fixed
sd4: 9314 GB, 65535 cyl, 255 head, 1168 sec, 512 bytes/sect x
19534592432 sectors
As you can see, I only had a valid GPT table on the first of these
devices which was created by a Linux system using parted.
gpt shows this:
# gpt show /dev/rsd1
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 19534592365
19534592399 32 Sec GPT table
19534592431 1 Sec GPT header
#
Now I want to use them inside NetBSD, but mbrlabel already shows strange
partition sizes:
# mbrlabel sd1
Found unknown partition; size 4294967295 (2097151 MB), offset 1
skipping existing unknown partition at slot a.
4 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 4294967295 1 unknown # (Cyl.
0*- 4294967295)
d: 2354723248 0 unused 0 0 # (Cyl. 0
- 7906*)
Not updating disk label.
#
But even if I try to use it, I cannot newfs the devices:
# disklabel sd1
# /dev/rsd1d:
type: SCSI
disk: LOGICAL VOLUME
label: fictitious
flags:
bytes/sector: 512
sectors/track: 1168
tracks/cylinder: 255
sectors/cylinder: 297840
cylinders: 65535
total sectors: 2354723248
rpm: 15000
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
4 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 4294967295 1 unknown # (Cyl.
0*- 4294967295)
d: 2354723248 0 unused 0 0 # (Cyl. 0
- 7906*)
# newfs /dev/rsd1a
newfs: /dev/rsd1a: open for read: Device busy
Is there a size limitation in the use of BSD disklabels? I trad
something about 1TB using Google, but this thread was rather old and
claimed that this is a problem of 32bit systems.
Can anybody give me an advice if these devices can be used inside NetBSD?
And speaking about large disks, what would be an appropreate file system?
Thanks for any hint and best regards,
Torsten
P.S.: # uname -a
NetBSD livecd.jibbed.org 5.0_STABLE NetBSD 5.0_STABLE (JIBBED5) #0: Sat
May 9 16:18:52 CEST 2009
root%amd64.aydogan.net@localhost:/root/livecd/work/JIBBED5 amd64
--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<> <>
<> Dr. Torsten Harenberg harenberg%physik.uni-wuppertal.de@localhost <>
<> Bergische Universitaet <>
<> FB C - Physik Tel.: +49 (0)202 439-3521 <>
<> Gaussstr. 20 Fax : +49 (0)202 439-2811 <>
<> 42097 Wuppertal <>
<> <>
<><><><><><><>< Of course it runs NetBSD http://www.netbsd.org ><>
Home |
Main Index |
Thread Index |
Old Index