doh, of course it works that way

Having grown up with raw devices I never considered the possibility of growing a dbspace - how can you make a physical device larger? But the question just came up and I just walked through a proof and if the device is a cooked file, of course you can grow the device, just use the -o (offset) flag. Here: $ touch junk_spc $ chmod 660 junk_spc $ ls -l junk_spc -rw-rw---- 1 informix informix 0 Aug 14 14:09 junk_spc $ onspaces -c -d junk_spc -p /dsk3/data/junk_spc -s 1000 -o 0Verifying physical disk space, please wait ... Space successfully added. ** WARNING ** A level 0 archive of Root DBSpace will need to be done. $ ls -l junk_spc -rw-rw---- 1 informix informix 1024000 Aug 14 14:11 junk_spc $ onspaces -a junk_spc -p /dsk3/data/junk_spc -s 1000 -o 1000Verifying physical disk space, please wait ... Chunk successfully added. $ ls -l junk_spc -rw-rw---- 1 informix informix 2048000 Aug 14 14:11 junk_spc onstat -d .........4e8b52b8 9 0x60001 9 2 2048 N B informix junk_spc ......... 4e8b5418 9 9 0 500 447 PO-B /dsk3/data/junk_spc 4e8b5840 10 9 500 500 497 PO-B /dsk3/data/junk_spc Of course it shows up as two chunks, and you do have to pay attention to convert between OS filesizes and Informix sizes, but how cute is that? j.

This is interesting, what version of IDS is it? I always thought the "book" said we can't (or should not) off-set cooked devices. So did you try creating a ~2MB tables in this "junk" dbspace and load data into it? did it work for you? ----- Original Message ---- From: "jack.parker4@verizon.net" <jack.parker4@verizon.net> To: ids@iiug.org Sent: Thursday, August 14, 2008 2:16:42 PM Subject: doh, of course it works that way [13106] Having grown up with raw devices I never considered the possibility of growing a dbspace - how can you make a physical device larger? But the question just came up and I just walked through a proof and if the device is a cooked file, of course you can grow the device, just use the -o (offset) flag. Here: $ touch junk_spc $ chmod 660 junk_spc $ ls -l junk_spc -rw-rw---- 1 informix informix 0 Aug 14 14:09 junk_spc $ onspaces -c -d junk_spc -p /dsk3/data/junk_spc -s 1000 -o 0Verifying physical disk space, please wait ... Space successfully added. ** WARNING ** A level 0 archive of Root DBSpace will need to be done. $ ls -l junk_spc -rw-rw---- 1 informix informix 1024000 Aug 14 14:11 junk_spc $ onspaces -a junk_spc -p /dsk3/data/junk_spc -s 1000 -o 1000Verifying physical disk space, please wait ... Chunk successfully added. $ ls -l junk_spc -rw-rw---- 1 informix informix 2048000 Aug 14 14:11 junk_spc onstat -d ..........4e8b52b8 9 0x60001 9 2 2048 N B informix junk_spc .......... 4e8b5418 9 9 0 500 447 PO-B /dsk3/data/junk_spc 4e8b5840 10 9 500 500 497 PO-B /dsk3/data/junk_spc Of course it shows up as two chunks, and you do have to pay attention to convert between OS filesizes and Informix sizes, but how cute is that? j. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

You can use offsets just fine with RAW or COOKED devices (or even filesystem files, but that's just weird! ;-} It has always worked. Art On Thu, Aug 14, 2008 at 2:47 PM, Kern Doe <kern_doe@yahoo.com> wrote: > This is interesting, what version of IDS is it? I always thought the "book" > said we can't (or should not) off-set cooked devices. So did you try > creating > a ~2MB tables in this "junk" dbspace and load data into it? did it work for > you? > > ----- Original Message ---- > From: "jack.parker4@verizon.net" <jack.parker4@verizon.net> > To: ids@iiug.org > Sent: Thursday, August 14, 2008 2:16:42 PM > Subject: doh, of course it works that way [13106] > > Having grown up with raw devices I never considered the possibility of > growing a dbspace - how can you make a physical device larger? But the > question just came up and I just walked through a proof and if the > device is a cooked file, of course you can grow the device, just use the > -o (offset) flag. Here: > > $ touch junk_spc > $ chmod 660 junk_spc > $ ls -l junk_spc > -rw-rw---- 1 informix informix 0 Aug 14 14:09 junk_spc > $ onspaces -c -d junk_spc -p /dsk3/data/junk_spc -s 1000 -o 0> Verifying physical disk space, please wait ... > Space successfully added. > > ** WARNING ** A level 0 archive of Root DBSpace will need to be done. > $ ls -l junk_spc > -rw-rw---- 1 informix informix 1024000 Aug 14 14:11 junk_spc > $ onspaces -a junk_spc -p /dsk3/data/junk_spc -s 1000 -o 1000> Verifying physical disk space, please wait ... > Chunk successfully added. > $ ls -l junk_spc > -rw-rw---- 1 informix informix 2048000 Aug 14 14:11 junk_spc> > onstat -d > ...........> 4e8b52b8 9 0x60001 9 2 2048 N B > informix junk_spc > > ........... > 4e8b5418 9 9 0 500 447 PO-B > /dsk3/data/junk_spc > 4e8b5840 10 9 500 500 497 PO-B > /dsk3/data/junk_spc > > Of course it shows up as two chunks, and you do have to pay attention to > convert between OS filesizes and Informix sizes, but how cute is that? > > j. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.