Befuddled

9.40 FC8 HPUX 11.11 OK, this is strange. I've linked a new 2 gig device called '/dev/informix/hold4'. The raw device is 2 gig's. Prior to creating the new link I performed both a fuser -f & an inode check to confirm the device is not in use. I then attempted to create many new 100 meg dbspace using onspaces script below (using offsets - these are inactive psoft tables). At the first creation (and all subsequent creates) I experience "cannot build space no free space." Of course I know the device is totally free. I've looked at rootdbs and I have plenty free, temp dbspaces are all unused. Any one have any other ideas. BTW, my total number devices prior to this is only 365 and I'm seeing this same problem with 3 other newly linked 2 gig devices. rootdbs free: Wed Jan 17 15:32:09 EST 2007 # Name Size Pages free Kfree MB Used MB Free %free 1 rootdbs 60000 44335 88670 30.60 86.59 73.89 * $ onspaces -c -d eoculrg -p /dev/informix/hold4 -o 0 -s 100000Verifying physical disk space, please wait ... Cannot build a new Space. ISAM error: no free disk space onspaces -c -d eoculrg -p /dev/informix/hold4 -o 0 -s 100000 onspaces -c -d eodsapp -p /dev/informix/hold4 -o 101000 -s 100000 onspaces -c -d eodslrg -p /dev/informix/hold4 -o 201000 -s 100000 onspaces -c -d eoecapp -p /dev/informix/hold4 -o 301000 -s 100000 onspaces -c -d eoeclrg -p /dev/informix/hold4 -o 401000 -s 100000 onspaces -c -d eoecwrk -p /dev/informix/hold4 -o 501000 -s 100000 onspaces -c -d eoeiapp -p /dev/informix/hold4 -o 601000 -s 100000 onspaces -c -d eoeilrg -p /dev/informix/hold4 -o 701000 -s 100000 onspaces -c -d eoepapp -p /dev/informix/hold4 -o 801000 -s 100000 onspaces -c -d eoeplrg -p /dev/informix/hold4 -o 901000 -s 100000 onspaces -c -d eoepwrk -p /dev/informix/hold4 -o1001000 -s 100000 onspaces -c -d eoewapp -p /dev/informix/hold4 -o1101000 -s 100000 onspaces -c -d eoewlrg -p /dev/informix/hold4 -o1201000 -s 100000 onspaces -c -d eoewwrk -p /dev/informix/hold4 -o1301000 -s 100000 onspaces -c -d eoiuapp -p /dev/informix/hold4 -o1401000 -s 100000 onspaces -c -d eoiulrg -p /dev/informix/hold4 -o1501000 -s 100000 onspaces -c -d eoiuwrk -p /dev/informix/hold4 -o1601000 -s 100000 onspaces -c -d eolarge -p /dev/informix/hold4 -o1701000 -s 100000 onspaces -c -d eoppapp -p /dev/informix/hold4 -o1901000 -s 100000

Darren_Jacobs@carmax.com wrote: > 9.40 FC8 > HPUX 11.11 > > OK, this is strange. I've linked a new 2 gig device called > '/dev/informix/hold4'. The raw device is 2 gig's. Prior to creating the > new link I performed both a fuser -f & an inode check to confirm the device > is not in use. I then attempted to create many new 100 meg dbspace using > onspaces script below (using offsets - these are inactive psoft tables). > At the first creation (and all subsequent creates) I experience "cannot > build space no free space." Of course I know the device is totally free. > I've looked at rootdbs and I have plenty free, temp dbspaces are all > unused. > > Any one have any other ideas. BTW, my total number devices prior to this > is only 365 and I'm seeing this same problem with 3 other newly linked 2 > gig devices. > > rootdbs free: > Wed Jan 17 15:32:09 EST 2007 > # Name Size Pages free Kfree MB Used MB Free > %free > 1 rootdbs 60000 44335 88670 30.60 86.59 > 73.89 * > > $ onspaces -c -d eoculrg -p /dev/informix/hold4 > -o 0 -s 100000> Verifying physical disk space, please wait ... > Cannot build a new Space. > ISAM error: no free disk space <SNIP> Can you dd to the device for 100000K without error? dd of=/dev/informix/hold4 bs=1k count=100000 Also why the 100K gap between chunks? Art S. Kagel

responses are below. Darren_Jacobs@carmax.com wrote: > 9.40 FC8 > HPUX 11.11 > > OK, this is strange. I've linked a new 2 gig device called > '/dev/informix/hold4'. The raw device is 2 gig's. Prior to creating the > new link I performed both a fuser -f & an inode check to confirm the device > is not in use. I then attempted to create many new 100 meg dbspace using > onspaces script below (using offsets - these are inactive psoft tables). > At the first creation (and all subsequent creates) I experience "cannot > build space no free space." Of course I know the device is totally free. > I've looked at rootdbs and I have plenty free, temp dbspaces are all > unused. > > Any one have any other ideas. BTW, my total number devices prior to this > is only 365 and I'm seeing this same problem with 3 other newly linked 2 > gig devices. > > rootdbs free: > Wed Jan 17 15:32:09 EST 2007 > # Name Size Pages free Kfree MB Used MB Free > %free > 1 rootdbs 60000 44335 88670 30.60 86.59 > 73.89 * > > $ onspaces -c -d eoculrg -p /dev/informix/hold4 > -o 0 -s 100000> Verifying physical disk space, please wait ... > Cannot build a new Space. > ISAM error: no free disk space <SNIP> Can you dd to the device for 100000K without error? dd of=/dev/informix/hold4 bs=1k count=100000 Also why the 100K gap between chunks? Art S. Kagel The gaps are probably 2 things, bad math on my part and using excel to quickly gen the script. I did figure out the problem and it does involve the rootdbs space. The original size of rootdbs was 20 meg. Since I started using onbar I had to increase the size of root by 100 meg. For some reason the extra freespace was not being utilized when adding the new spaces. What I did (maybe a good idea or not) was run buildsmi. Was was then able to add all new devices. Now the question is - why would onspaces croak if there is available space but maybe on a different root chunk? Any ideas now? BTW, thanks for the quick responses. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list

the engine has 2 system reserved pages tro store chunks and dbspaces. when these pages are full it'll allocate extended system reserved pages in order to store more wanted chunks/dbspaces. so no space left in rootdbs first chunk can cause this. afaikr it'll only look for space in rootdbs first chunk.... maybe this has changed in 10??? Superboer, Darren_Jacobs@carmax.com schreef: > responses are below. > > > > > Darren_Jacobs@carmax.com wrote: > > 9.40 FC8 > > HPUX 11.11 > > > > OK, this is strange. I've linked a new 2 gig device called > > '/dev/informix/hold4'. The raw device is 2 gig's. Prior to creating the > > new link I performed both a fuser -f & an inode check to confirm the > device > > is not in use. I then attempted to create many new 100 meg dbspace using > > onspaces script below (using offsets - these are inactive psoft tables). > > At the first creation (and all subsequent creates) I experience "cannot > > build space no free space." Of course I know the device is totally free. > > I've looked at rootdbs and I have plenty free, temp dbspaces are all > > unused. > > > > Any one have any other ideas. BTW, my total number devices prior to this > > is only 365 and I'm seeing this same problem with 3 other newly linked 2 > > gig devices. > > > > rootdbs free: > > Wed Jan 17 15:32:09 EST 2007 > > # Name Size Pages free Kfree MB Used MB Free > > %free > > 1 rootdbs 60000 44335 88670 30.60 86.59 > > 73.89 * > > > > $ onspaces -c -d eoculrg -p /dev/informix/hold4 > > -o 0 -s 100000> > Verifying physical disk space, please wait ... > > Cannot build a new Space. > > ISAM error: no free disk space > <SNIP>> > Can you dd to the device for 100000K without error? > > dd of=/dev/informix/hold4 bs=1k count=100000 > > Also why the 100K gap between chunks? > > Art S. Kagel > > The gaps are probably 2 things, bad math on my part and using excel to > quickly gen the script. > > I did figure out the problem and it does involve the rootdbs space. The > original size of rootdbs was 20 meg. Since I started using onbar I had to > increase the size of root by 100 meg. For some reason the extra freespace > was not being utilized when adding the new spaces. What I did (maybe a > good idea or not) was run buildsmi. Was was then able to add all new > devices. > > Now the question is - why would onspaces croak if there is available space > but maybe on a different root chunk? > > Any ideas now? > > BTW, thanks for the quick responses. > > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list

\