Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
A user asked what size to specify when adding a chunk so a 2 GB raw partition is fully used. The answer: onspaces takes KB, not pages (e.g. onspaces -a dbspace -p /dev/raw -o 0 -s <size in KB>), and onmonitor shows KB in 9.30 though the poster's Informix 7 onmonitor shows pages. Others corrected the 2 GB figure from 2048000 to about 2097150 KB, noting that if you specify too large a value the engine reports the real maximum, and you may need to round down a few KB to a multiple of the page size.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
I've been adding chunks to Informix using the incorrect size
to fully use a disk partition. I am going to start using the
correct size now (and correct the old ones at a later date).
Now I have 2Gb raw disk partitions. If I want to add an additional
chunk to a dbspace do I set the block size as 1024000 to fully use
the filesystem?
Hope someone can help.
↪ replying to Geezer From The Freezer
John Carlson — — source: Usenet: comp.databases.informix
On Wed, 19 Nov 2003 14:55:42 +0000, Geezer From The Freezer
<Geezer@Freezer.com> wrote:
>I've been adding chunks to Informix using the incorrect size
>to fully use a disk partition. I am going to start using the
>correct size now (and correct the old ones at a later date).
>
>Now I have 2Gb raw disk partitions. If I want to add an additional
>chunk to a dbspace do I set the block size as 1024000 to fully use
>the filesystem?
>
If I understand you correctly.......8-)
In order to use the full 2G rawspace as a chunk for a dbspace, you
would use something like . . .
onspaces -a (some dbspace_name) -p (path to raw disk
partition) -o 0 -s 2048000
This would add a 2G chunk to a dbspace. Remember, onspaces uses K,
not pages.
HTH
JWC
John Carlson wrote:
> This would add a 2G chunk to a dbspace. Remember, onspaces uses K,
> not pages.
John - what about onmonitor?
↪ replying to Geezer From The Freezer
John Carlson — — source: Usenet: comp.databases.informix
On Wed, 19 Nov 2003 15:42:15 +0000, Geezer From The Freezer
<Geezer@Freezer.com> wrote:
>
>
>John Carlson wrote:
>
>> This would add a 2G chunk to a dbspace. Remember, onspaces uses K,
>> not pages.
>
>
>John - what about onmonitor?
Ooooooh, good point . . . . I haven't used onmonitor in ages....
According to the onmonitor screen I see in 9.30, it shows KB for
offset and size.
John Carlson wrote:
>
> On Wed, 19 Nov 2003 15:42:15 +0000, Geezer From The Freezer
> <Geezer@Freezer.com> wrote:
> >John - what about onmonitor?
>
> Ooooooh, good point . . . . I haven't used onmonitor in ages....
>
> According to the onmonitor screen I see in 9.30, it shows KB for
> offset and size.
hmm mine shows "Pages in chunk" then again I'm on informix 7
"John Carlson" <john_carlson@whsmithusa.com> wrote in message
news:082nrvofm8f0ibnkfi9gkb2ml0584ephga@4ax.com...
> On Wed, 19 Nov 2003 14:55:42 +0000, Geezer From The Freezer
> <Geezer@Freezer.com> wrote:
>
> >I've been adding chunks to Informix using the incorrect size
> >to fully use a disk partition.
> In order to use the full 2G rawspace as a chunk for a dbspace, you
> would use something like . . .
> onspaces -a (some dbspace_name) -p (path to raw disk
> partition) -o 0 -s 2048000
2097150 in fact.
↪ replying to John Carlson
Andy Kent — — source: Usenet: comp.databases.informix
> In order to use the full 2G rawspace as a chunk for a dbspace, you
> would use something like . . .
> onspaces -a (some dbspace_name) -p (path to raw disk
> partition) -o 0 -s 2048000>
> This would add a 2G chunk to a dbspace.
It would add somewhat less than 2GB. The full size is (from memory)
2097150K.
If you try too big a number it'll tell you the actual maximum. You'll
probably have to deduct 1 - 3k to make the figure it tells you a
multiple of page size.
Andy
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.