creating a new disk group in Tru64

[Alphaserver]

Hello all;
I have an ES45 running Tru64 5.1b. A SmarArray 5300A with 1 existing 400gb lun (known as dg pdsdg) and I added 7 new 300gb disks to the shelf, created a second lun in the on board utility (1.34tb). Booted the system , it generated devices dsk2a,b,c,d..... all good so far.
I went disklabeled -nr /dev/rdisk/dsk2c. (entire disk)
Went into sysman- lsm management, created a new disk group (disk2dg) added my new disk dsk2c. Problem is it seems to have no free space available..
ie volassist -g disk2dg make space 40g

fails... ideas? did I miss something? thanks all.

[Venkatesh BL]

Can you post the output of 'volprint'? What is the OS/patch version?

[Alphaserver]

Sure... here is volprint output.
My new disk group is disk2dg
# volprint
Disk group: rootdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg rootdg rootdg - - - - - -

dm dsk0d dsk0d - 0 - - - -
dm root01 dsk0a - 786432 - - - -
dm swap01 dsk0b - 786432 - - - -
dm usr01 dsk0g - 4300800 - - - -

v rootvol root ENABLED 786432 - ACTIVE - -
pl rootvol-01 rootvol ENABLED 786432 - ACTIVE - -
sd root01-01 rootvol-01 ENABLED 786432 0 - - -

v swapvol swap ENABLED 786432 - ACTIVE - -
pl swapvol-01 swapvol ENABLED 786432 - ACTIVE - -
sd swap01-01 swapvol-01 ENABLED 786432 0 - - -

v usrvol fsgen ENABLED 4300800 - ACTIVE - -
pl usrvol-01 usrvol ENABLED 4300800 - ACTIVE - -
sd usr01-01 usrvol-01 ENABLED 4300800 0 - - -

Disk group: disk2dg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg disk2dg disk2dg - - - - - -

dm dsk2 dsk2c - 0 - - - -

Disk group: pdsdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg pdsdg pdsdg - - - - - -

dm dsk1 dsk1 - 711305893 - - - -

v apg fsgen ENABLED 20480000 - ACTIVE - -
pl apg-01 apg ENABLED 20480000 - ACTIVE - -
sd dsk1-02 apg-01 ENABLED 20480000 0 - - -

v job_table fsgen ENABLED 307200 - ACTIVE - -
pl job_table-01 job_table ENABLED 307200 - ACTIVE - -
sd dsk1-03 job_table-01 ENABLED 307200 0 - - -

v pds_oracle fsgen ENABLED 204800000 - ACTIVE - -
pl pds_oracle-01 pds_oracle ENABLED 204800000 - ACTIVE - -
sd dsk1-06 pds_oracle-01 ENABLED 204800000 0 - - -

v pdscustom fsgen ENABLED 4096000 - ACTIVE - -
pl pdscustom-01 pdscustom ENABLED 4096000 - ACTIVE - -
sd dsk1-04 pdscustom-01 ENABLED 4096000 0 - - -

v space fsgen ENABLED 62914560 - ACTIVE - -
pl space-01 space ENABLED 62914560 - ACTIVE - -
sd dsk1-07 space-01 ENABLED 62914560 0 - - -

v space01 fsgen ENABLED 83886080 - ACTIVE - -
pl space01-01 space01 ENABLED 83886080 - ACTIVE - -
sd dsk1-08 space01-01 ENABLED 83886080 0 - - -

v space02 fsgen ENABLED 83886080 - ACTIVE - -
pl space02-01 space02 ENABLED 83886080 - ACTIVE - -
sd dsk1-09 space02-01 ENABLED 83886080 0 - - -

v space03 fsgen ENABLED 83886080 - ACTIVE - -
pl space03-01 space03 ENABLED 83886080 - ACTIVE - -
sd dsk1-10 space03-01 ENABLED 83886080 0 - - -

v space04 fsgen ENABLED 83886080 - ACTIVE - -
pl space04-01 space04 ENABLED 83886080 - ACTIVE - -
sd dsk1-11 space04-01 ENABLED 83886080 0 - - -

v swap_vol01 fsgen ENABLED 15990784 - ACTIVE - -
pl swap_vol01-01 swap_vol01 ENABLED 15990784 - ACTIVE - -
sd dsk1-01 swap_vol01-01 ENABLED 15990784 0 - - -

v swap_vol02 fsgen ENABLED 16777216 - ACTIVE - -
pl swap_vol02-01 swap_vol02 ENABLED 16777216 - ACTIVE - -
sd dsk1-12 swap_vol02-01 ENABLED 16777216 0 - - -

v u01 fsgen ENABLED 20480000 - ACTIVE - -
pl u01-01 u01 ENABLED 20480000 - ACTIVE - -
sd dsk1-05 u01-01 ENABLED 20480000 0 - - -
#

[Kapil Jha]

hi
What you tryin to do from this command if u r trying to make a volume its wrong one????

volassist -g disk2dg make space 40g

[Hein van den Heuvel]

Hmm,

Personally I would step back and retry with presenting a lun less than 1TB, specially if you are going to carve it up later anyway.

You indicate v5.1b, which best I can tell should support 2TB drives, but still... why go where noone else has gone before?

The smartarray can present those 7 drives as mutliple luns no?

Here is what google found for +tru64 +"maximum disk":

"v5.1 has a 1TB limit. Anything larger starts to run into problems with
the disk drivers for the physical disks. The logical block address is
passed as a signed 32 number so (2^31 - 1) * 512 = 1TB-512. Anything
larger than that and negative values get passed into the device drivers
and they do bad things.


v5.1a w/pk3 and beyond can go up to 2TB, and then it will run out of
gas. The 32 bit value was made unsigned and any places in the drivers
where it would care, were fixed, so now the value can (2^32 -1) * 512 =
2TB-512.


If you have the AdvFS license, you can use addvol to create file systems
that can be up to 256TB in size (512TB on v5.1a w/pk3). Individual
files on AdvFS can be 16TB.


I do not know much about LSM. I do not know if LSM can create logical
volume greater than 1TB either before or after v5.1a w/pk3. Someone
with more LSM knowledge would have to provide that answer.

Bob Harris "

And Bob harris is 'the man'. Trust him.

You may also want to look at the SPD's but they appear not to cover 5.1b.

Tru64:
http://h18000.www1.hp.com/info/SP7070/SP7070PF.PDF

LSM:
http://h18002.www1.hp.com/info/SP5124/SP5124PF.PDF

Release notes?
http://h30097.www3.hp.com/docs/pub_page/V51B_DOCS/V51B_DOCLIST.HTM

hth,
Hein.