Lost chunk/dbspace space

Anybody have any ideas on this? Thanks, Randy -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kennedy, Randy Sent: Tuesday, November 23, 2010 10:44 AM To: ids@iiug.org Subject: Lost chunk/dbspace space [22024] We have moved from an HP/UX 9.4FC3, physical server/drive environment to a RHEL 5, 11.1FC3 (no option to go to 11.5 or 11.7) VM server/SAN storage environment. In HP/UX, I used SAM to create logical volumes of raw disk space and then used symbolic links to create the chunks for Informix. I tried to mirror that setup for the new server and believe I have done so, but when I try to create my spaces/chunks, I cannot create them anywhere near the size that I created the 'space' as. For example, I created a 2048MB piece of space (partition 11 below), linked a raw device to it, created my symbolic link to the raw device, but when I try and create a dbspace in it, the largest size that it allows in 1952MB (anything larger returns an error of "the chunk <symbolic linked file name> will not fit in the space specified") Any clue as to where the extra space is going or if I am creating them wrong? I used parted to partition out the large VM hard drive (made up of SAN space) that the server is aware of. Here is the parted view of the drive. I created partition 4 as the container for all the DB storage, then subdivided that into partitions 5-13. 1-3 are used for server OS and filesystem needs. GNU Parted 1.8.1 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: VMware Virtual disk (scsi) Disk /dev/sda: 69.8GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 9434MB 9434MB primary ext3 boot 2 9434MB 14.7GB 5240MB primary ext3 3 14.7GB 16.8GB 2097MB primary linux-swap 4 16.8GB 62.9GB 46.1GB extended lba 5 16.8GB 20.9GB 4096MB logical 6 20.9GB 21.9GB 1028MB logical 7 21.9GB 25.0GB 3072MB logical 8 25.0GB 25.5GB 500MB logical 9 25.5GB 25.6GB 100MB logical 13 25.6GB 25.9GB 350MB logical 10 25.9GB 26.2GB 250MB logical 11 26.2GB 28.2GB 2048MB logical 12 28.2GB 53.8GB 25.6GB logical Doing this gave me /dev/sda4-13 block devices brw-r----- 1 root disk 8, 0 Nov 23 09:39 sda brw-rw---- 1 informix informix 8, 1 Nov 23 09:39 sda1 brw-rw---- 1 informix informix 8, 10 Nov 23 09:39 sda10 brw-rw---- 1 informix informix 8, 11 Nov 23 10:09 sda11 brw-rw---- 1 informix informix 8, 12 Nov 23 09:39 sda12 brw-rw---- 1 informix informix 8, 13 Nov 23 09:39 sda13 brw-r----- 1 root disk 8, 2 Nov 23 09:39 sda2 brw-r----- 1 root disk 8, 3 Nov 23 09:39 sda3 brw-r----- 1 informix informix 8, 4 Nov 23 09:39 sda4 brw-r----- 1 informix informix 8, 5 Nov 23 09:39 sda5 brw-r----- 1 informix informix 8, 6 Nov 23 09:39 sda6 brw-r----- 1 informix informix 8, 7 Nov 23 09:39 sda7 brw-r----- 1 informix informix 8, 8 Nov 23 09:39 sda8 brw-r----- 1 informix informix 8, 9 Nov 23 09:39 sda9 I then used raw to create the character devices. /dev/raw/raw1: bound to major 8, minor 5 /dev/raw/raw2: bound to major 8, minor 6 /dev/raw/raw3: bound to major 8, minor 7 /dev/raw/raw4: bound to major 8, minor 8 /dev/raw/raw5: bound to major 8, minor 13 /dev/raw/raw6: bound to major 8, minor 10 /dev/raw/raw7: bound to major 8, minor 11 /dev/raw/raw8: bound to major 8, minor 12 I then used the characters devices for my symbolic links lrwxrwxrwx 1 informix informix 13 Nov 17 14:34 casedatadbs -> /dev/raw/raw8 lrwxrwxrwx 1 informix informix 13 Nov 17 14:32 commondbs -> /dev/raw/raw6 lrwxrwxrwx 1 informix informix 13 Nov 16 12:22 dwdbs -> /dev/raw/raw3 lrwxrwxrwx 1 informix informix 13 Nov 16 12:22 llogsdbs -> /dev/raw/raw4 lrwxrwxrwx 1 informix informix 13 Nov 17 14:30 rootdbs -> /dev/raw/raw5 lrwxrwxrwx 1 informix informix 13 Nov 11 14:29 tempdbs -> /dev/raw/raw1 lrwxrwxrwx 1 informix informix 13 Nov 16 12:21 testdbs -> /dev/raw/raw2 lrwxrwxrwx 1 informix informix 10 Nov 23 10:05 working2dbs -> /dev/sda11 lrwxrwxrwx 1 informix informix 13 Nov 17 14:33 workingdbs -> /dev/raw/raw7 I then used the symbolic link file path for the dbspace creation. =>onspaces -c -d workingdbs -p /db/links/workingdbs -o 0 -s 2097152 Verifying physical disk space, please wait ... The chunk '/db/links/workingdbs' will not fit in the space specified. TIA, Randy

Sounds a bit like a kilobyte isn´t 1024 byte, but 1000 byte to me. Joerg Volz ----------------------------------------------------------------------------- -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kennedy, Randy Sent: Monday, November 29, 2010 8:31 PM To: ids@iiug.org Subject: Lost chunk/dbspace space [22086] Anybody have any ideas on this? Thanks, Randy -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kennedy, Randy Sent: Tuesday, November 23, 2010 10:44 AM To: ids@iiug.org Subject: Lost chunk/dbspace space [22024] We have moved from an HP/UX 9.4FC3, physical server/drive environment to a RHEL 5, 11.1FC3 (no option to go to 11.5 or 11.7) VM server/SAN storage environment. In HP/UX, I used SAM to create logical volumes of raw disk space and then used symbolic links to create the chunks for Informix. I tried to mirror that setup for the new server and believe I have done so, but when I try to create my spaces/chunks, I cannot create them anywhere near the size that I created the 'space' as. For example, I created a 2048MB piece of space (partition 11 below), linked a raw device to it, created my symbolic link to the raw device, but when I try and create a dbspace in it, the largest size that it allows in 1952MB (anything larger returns an error of "the chunk <symbolic linked file name> will not fit in the space specified") Any clue as to where the extra space is going or if I am creating them wrong? I used parted to partition out the large VM hard drive (made up of SAN space) that the server is aware of. Here is the parted view of the drive. I created partition 4 as the container for all the DB storage, then subdivided that into partitions 5-13. 1-3 are used for server OS and filesystem needs. GNU Parted 1.8.1 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: VMware Virtual disk (scsi) Disk /dev/sda: 69.8GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 9434MB 9434MB primary ext3 boot 2 9434MB 14.7GB 5240MB primary ext3 3 14.7GB 16.8GB 2097MB primary linux-swap 4 16.8GB 62.9GB 46.1GB extended lba 5 16.8GB 20.9GB 4096MB logical 6 20.9GB 21.9GB 1028MB logical 7 21.9GB 25.0GB 3072MB logical 8 25.0GB 25.5GB 500MB logical 9 25.5GB 25.6GB 100MB logical 13 25.6GB 25.9GB 350MB logical 10 25.9GB 26.2GB 250MB logical 11 26.2GB 28.2GB 2048MB logical 12 28.2GB 53.8GB 25.6GB logical Doing this gave me /dev/sda4-13 block devices brw-r----- 1 root disk 8, 0 Nov 23 09:39 sda brw-rw---- 1 informix informix 8, 1 Nov 23 09:39 sda1 brw-rw---- 1 informix informix 8, 10 Nov 23 09:39 sda10 brw-rw---- 1 informix informix 8, 11 Nov 23 10:09 sda11 brw-rw---- 1 informix informix 8, 12 Nov 23 09:39 sda12 brw-rw---- 1 informix informix 8, 13 Nov 23 09:39 sda13 brw-r----- 1 root disk 8, 2 Nov 23 09:39 sda2 brw-r----- 1 root disk 8, 3 Nov 23 09:39 sda3 brw-r----- 1 informix informix 8, 4 Nov 23 09:39 sda4 brw-r----- 1 informix informix 8, 5 Nov 23 09:39 sda5 brw-r----- 1 informix informix 8, 6 Nov 23 09:39 sda6 brw-r----- 1 informix informix 8, 7 Nov 23 09:39 sda7 brw-r----- 1 informix informix 8, 8 Nov 23 09:39 sda8 brw-r----- 1 informix informix 8, 9 Nov 23 09:39 sda9 I then used raw to create the character devices. /dev/raw/raw1: bound to major 8, minor 5 /dev/raw/raw2: bound to major 8, minor 6 /dev/raw/raw3: bound to major 8, minor 7 /dev/raw/raw4: bound to major 8, minor 8 /dev/raw/raw5: bound to major 8, minor 13 /dev/raw/raw6: bound to major 8, minor 10 /dev/raw/raw7: bound to major 8, minor 11 /dev/raw/raw8: bound to major 8, minor 12 I then used the characters devices for my symbolic links lrwxrwxrwx 1 informix informix 13 Nov 17 14:34 casedatadbs -> /dev/raw/raw8 lrwxrwxrwx 1 informix informix 13 Nov 17 14:32 commondbs -> /dev/raw/raw6 lrwxrwxrwx 1 informix informix 13 Nov 16 12:22 dwdbs -> /dev/raw/raw3 lrwxrwxrwx 1 informix informix 13 Nov 16 12:22 llogsdbs -> /dev/raw/raw4 lrwxrwxrwx 1 informix informix 13 Nov 17 14:30 rootdbs -> /dev/raw/raw5 lrwxrwxrwx 1 informix informix 13 Nov 11 14:29 tempdbs -> /dev/raw/raw1 lrwxrwxrwx 1 informix informix 13 Nov 16 12:21 testdbs -> /dev/raw/raw2 lrwxrwxrwx 1 informix informix 10 Nov 23 10:05 working2dbs -> /dev/sda11 lrwxrwxrwx 1 informix informix 13 Nov 17 14:33 workingdbs -> /dev/raw/raw7 I then used the symbolic link file path for the dbspace creation. =>onspaces -c -d workingdbs -p /db/links/workingdbs -o 0 -s 2097152 Verifying physical disk space, please wait ... The chunk '/db/links/workingdbs' will not fit in the space specified. TIA, Randy ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. IT Handel und Beratung Jörg Volz Bernhard-Früh-Str. 7 77855 Achern GERMANY Tel: +49 (0)7841-681651 Fax: +49 (0)7841-681654 Mobil: +49 (0)170-2989757 VAT-ID: DE201383541 http://www.it-volz.de

Doh!, yes, that was the issue. Once we got parted to show the sizes in Bytes instead of MB and did the calculations, it shows 2048MB as ~2048000000B. We recreated all of our partitions using Byte sizes and now the spaces fit fine. Thank you. Thanks, Randy -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Joerg Volz Sent: Monday, November 29, 2010 12:33 PM To: ids@iiug.org Subject: RE: Lost chunk/dbspace space [22087] Sounds a bit like a kilobyte isn´t 1024 byte, but 1000 byte to me. Joerg Volz ----------------------------------------------------------------------------- -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kennedy, Randy Sent: Monday, November 29, 2010 8:31 PM To: ids@iiug.org Subject: Lost chunk/dbspace space [22086] Anybody have any ideas on this? Thanks, Randy -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kennedy, Randy Sent: Tuesday, November 23, 2010 10:44 AM To: ids@iiug.org Subject: Lost chunk/dbspace space [22024] We have moved from an HP/UX 9.4FC3, physical server/drive environment to a RHEL 5, 11.1FC3 (no option to go to 11.5 or 11.7) VM server/SAN storage environment. In HP/UX, I used SAM to create logical volumes of raw disk space and then used symbolic links to create the chunks for Informix. I tried to mirror that setup for the new server and believe I have done so, but when I try to create my spaces/chunks, I cannot create them anywhere near the size that I created the 'space' as. For example, I created a 2048MB piece of space (partition 11 below), linked a raw device to it, created my symbolic link to the raw device, but when I try and create a dbspace in it, the largest size that it allows in 1952MB (anything larger returns an error of "the chunk <symbolic linked file name> will not fit in the space specified") Any clue as to where the extra space is going or if I am creating them wrong? I used parted to partition out the large VM hard drive (made up of SAN space) that the server is aware of. Here is the parted view of the drive. I created partition 4 as the container for all the DB storage, then subdivided that into partitions 5-13. 1-3 are used for server OS and filesystem needs. GNU Parted 1.8.1 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: VMware Virtual disk (scsi) Disk /dev/sda: 69.8GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 9434MB 9434MB primary ext3 boot 2 9434MB 14.7GB 5240MB primary ext3 3 14.7GB 16.8GB 2097MB primary linux-swap 4 16.8GB 62.9GB 46.1GB extended lba 5 16.8GB 20.9GB 4096MB logical 6 20.9GB 21.9GB 1028MB logical 7 21.9GB 25.0GB 3072MB logical 8 25.0GB 25.5GB 500MB logical 9 25.5GB 25.6GB 100MB logical 13 25.6GB 25.9GB 350MB logical 10 25.9GB 26.2GB 250MB logical 11 26.2GB 28.2GB 2048MB logical 12 28.2GB 53.8GB 25.6GB logical Doing this gave me /dev/sda4-13 block devices brw-r----- 1 root disk 8, 0 Nov 23 09:39 sda brw-rw---- 1 informix informix 8, 1 Nov 23 09:39 sda1 brw-rw---- 1 informix informix 8, 10 Nov 23 09:39 sda10 brw-rw---- 1 informix informix 8, 11 Nov 23 10:09 sda11 brw-rw---- 1 informix informix 8, 12 Nov 23 09:39 sda12 brw-rw---- 1 informix informix 8, 13 Nov 23 09:39 sda13 brw-r----- 1 root disk 8, 2 Nov 23 09:39 sda2 brw-r----- 1 root disk 8, 3 Nov 23 09:39 sda3 brw-r----- 1 informix informix 8, 4 Nov 23 09:39 sda4 brw-r----- 1 informix informix 8, 5 Nov 23 09:39 sda5 brw-r----- 1 informix informix 8, 6 Nov 23 09:39 sda6 brw-r----- 1 informix informix 8, 7 Nov 23 09:39 sda7 brw-r----- 1 informix informix 8, 8 Nov 23 09:39 sda8 brw-r----- 1 informix informix 8, 9 Nov 23 09:39 sda9 I then used raw to create the character devices. /dev/raw/raw1: bound to major 8, minor 5 /dev/raw/raw2: bound to major 8, minor 6 /dev/raw/raw3: bound to major 8, minor 7 /dev/raw/raw4: bound to major 8, minor 8 /dev/raw/raw5: bound to major 8, minor 13 /dev/raw/raw6: bound to major 8, minor 10 /dev/raw/raw7: bound to major 8, minor 11 /dev/raw/raw8: bound to major 8, minor 12 I then used the characters devices for my symbolic links lrwxrwxrwx 1 informix informix 13 Nov 17 14:34 casedatadbs -> /dev/raw/raw8 lrwxrwxrwx 1 informix informix 13 Nov 17 14:32 commondbs -> /dev/raw/raw6 lrwxrwxrwx 1 informix informix 13 Nov 16 12:22 dwdbs -> /dev/raw/raw3 lrwxrwxrwx 1 informix informix 13 Nov 16 12:22 llogsdbs -> /dev/raw/raw4 lrwxrwxrwx 1 informix informix 13 Nov 17 14:30 rootdbs -> /dev/raw/raw5 lrwxrwxrwx 1 informix informix 13 Nov 11 14:29 tempdbs -> /dev/raw/raw1 lrwxrwxrwx 1 informix informix 13 Nov 16 12:21 testdbs -> /dev/raw/raw2 lrwxrwxrwx 1 informix informix 10 Nov 23 10:05 working2dbs -> /dev/sda11 lrwxrwxrwx 1 informix informix 13 Nov 17 14:33 workingdbs -> /dev/raw/raw7 I then used the symbolic link file path for the dbspace creation. =>onspaces -c -d workingdbs -p /db/links/workingdbs -o 0 -s 2097152 Verifying physical disk space, please wait ... The chunk '/db/links/workingdbs' will not fit in the space specified. TIA, Randy ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. IT Handel und Beratung Jörg Volz Bernhard-Früh-Str. 7 77855 Achern GERMANY Tel: +49 (0)7841-681651 Fax: +49 (0)7841-681654 Mobil: +49 (0)170-2989757 VAT-ID: DE201383541 http://www.it-volz.de ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.