SEO

#1 (**permalink**) 01-05-2008, 09:08 AM

Hi,
I'm writing a program, which allocates storage, but a problem I have
run into is trying to get the true free size of a vpath/disk.
What I get using bootinfo -s vpath0 -> 8583
This is useable size of the disk? If we use a PP size of 32Mb we get
number of usable PP's -> 268.21 which rounds down to 268.

After we create a volume group using this vpath and another 78 disks
using params.

/usr/sbin/mkvg4vp -f -B -t 1 -y LARGE VG -s 32 vpath0 vpath1 vpath2
........

Oh I did also get a secondary problem, which was
/usr/sbin/mkvg4vp[227]: 27164 Memory fault(coredump)
I could not find any posts with this info on this problem either..
the volumegroup does look like it create ok though.

Now if I do a lspv -M vpath0 to display the pp map I get

#vpath0:1-267

So I get a difference of 1 pp between the bootinfo and the lspv on
vpaths on this server.

I have tried the same on a different server and do not get this
problem, but it does not have vpaths.
This discrepancy is throwing my calc. out. Any help on how to get the
true free size of a disk/vpath would be much appreciated.

#2 (**permalink**) 01-05-2008, 09:09 AM

did you create using -B on the other systems you tested on ?

Rgds
Mark Taylor

#3 (**permalink**) 01-05-2008, 09:09 AM

yup. I used -B and I also tried -G and it seem to return the size ok.
The only difference could be the size of the disks the other system had
smaller disks but the difference was 8G v 4G. I would not expect this
to cause such a problem? It has been driving me mad.
This problem means I cannot do any calcs. before creating a vg and in
order to create the vg I need to know how big the disks are so I can
allocate the lv's and then create the vg of the right size and disks..

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

free vpath disk sizes pre and post creation of a volume group can anyone explain please.