Disklabel size in V4.0F

[Francois Rabe]

I have a client that has a RAID5 disk consisting of 9 x 146GB. This gives just over a total of 1TB storage. They however seem to have a problem doing a disklabel on this disk. The question now is: What is the maximum size you can address in V4.0F? They would have to probably reduce the size and then use AdvFS and addvol.

[Michael Schulte zur Sur]

Hi,

could you post exact number and the disk label? You don't user advfs now?

greetings,

Michael

[Ralf Puchner]

Why not using the search function? Exactly the same question was made 2 days ago. Is it soo difficulty to use it?

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=645260

[Francois Rabe]

The search function WAS used by the way, but this did NOT answer my question. I asked a specific question in my post, and I quote, "The question now is: What is the maximum size you can address in V4.0F?" I also DID mention in my post that this volume is over 1TB in size. I am not that familiar with V4 of Tru64, hence I used this forum for an answer, not an insult. The output of a disklabel -r on this disk is the following, please note the size of the "C" partition.

type: SCSI
disk: i2o_bs
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 128
sectors/cylinder: 4096
cylinders: 35768
sectors/unit: -2000977920
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

8 partitions:
# size offset fstype [fsize bsize cpg] # NOTE:
values t
a: 131072 0 unused 0 0 # (Cyl. 0
- )
b: 262144 131072 unused 0 0 # (Cyl. 32
- )
c: -2000977920 0 unused 0 0 # (Cyl. 0
- )
d: 0 0 unused 0 0 # (Cyl. 0
- )
e: 0 0 unused 0 0 # (Cyl. 0
- )
f: 0 0 unused 0 0 # (Cyl. 0
- )
g: 1146798080 393216 unused 0 0 # (Cyl. 96
- )
h: 1146798080 1147191296 unused 0 0 # (Cyl.
280076 )

[Ralf Puchner]

have a look into the other thread, all your questions can be found there:

size: 1TB for ADVFS

disklabel info is irrelevant if controller doesn't support disksize, so use the scu command to check proper detection.

so first step is to check if hardware is supported if not - good luck you are out of specifications loosing support at all. next step is to check if controller properly returns device information (see other thread), next step is to check advfs limits (see other thread).

[Francois Rabe]

Thank you very much. :)