Re: raw device dbspace size >2GB

PaulITID.Matthews@chase.com wrote: > > Hazemb wrote: > > would someone please tell me If I can make a raw device dbspace with > size > > larger than 2GBytes ?? > > if I can't do this, pls. tell me why.. > > the platform I'm using is sun solaris 2.5.1 with IDS 7.2 ... > > > > I used to think that I can format the disk into slices larger than 2GB > (i.e. > > 3GB) and use the first 2GB of the slice as one dbspace, and then use the > last > > 1GB in another dbspace with offset set to 2GB, unfortunately it didn't > work > > !!!! > > > > honestly I don't know why, and it's very frustrating since I had to use > cocked > > files instead or otherwise I would have wasted a lot of space since I was > > limited by a max. number of partitions of 7 ( a UNIX constraint ). > > > > Hazem, > > You can use a raw device size as large as the disk, whatever that may be. > With raw disk 2GB is not a constraint. Not sure why your configration did > not work. It may be worth checking that your offset is not 0 as it will > overwrite the disk label and that the next offset does not overlap No you can't. The offset PLUS the size must not exceed 2GB. Split the disk into 2GB slices. Cheers, -- Mark. +----------------------------------------------------------+-----------+ |Mark D. Stock - Informix SA http://www.informix.com |//////// /| |mailto:mdstock@informix.com http://www.informix.com/idn |///// / //| |http://www.iiug.org +-----------------------------------+//// / ///| | Tel: +27 11 807 0313 |If it's slow, the users complain. |/// / ////| | Fax: +27 838250 2325 |If it's fast, the users keep quiet.|// / /////| |Cell: +27 83 250 2325 |Therefore, "No news: travels fast"!|/ ////////| +----------------------+-----------------------------------+-----------+

Hi Mark, Yes I see, but are you aware of any plans by Informix to change(correct) this situation ??? you're an insider man, use your influence.. : ) Regards, Hazem. mdstock@informix.com wrote: > > PaulITID.Matthews@chase.com wrote: > > > > You can use a raw device size as large as the disk, whatever that may be. > > With raw disk 2GB is not a constraint. Not sure why your configration did > > not work. It may be worth checking that your offset is not 0 as it will > > overwrite the disk label and that the next offset does not overlap > > No you can't. > > The offset PLUS the size must not exceed 2GB. Split the disk into 2GB > slices. > > Cheers, > -- > Mark. > > +----------------------------------------------------------+-----------+ > |Mark D. Stock - Informix SA http://www.informix.com |//////// /| > |mailto:mdstock@informix.com http://www.informix.com/idn |///// / //| > |http://www.iiug.org +-----------------------------------+//// / ///| > | Tel: +27 11 807 0313 |If it's slow, the users complain. |/// / ////| > | Fax: +27 838250 2325 |If it's fast, the users keep quiet.|// / /////| > |Cell: +27 83 250 2325 |Therefore, "No news: travels fast"!|/ ////////| > +----------------------+-----------------------------------+-----------+ > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

hazemb@my-dejanews.com wrote: > > Hi Mark, > Yes I see, but are you aware of any plans by Informix to change(correct) this > situation ??? > you're an insider man, use your influence.. > : ) The problem is not Informix's. Informix uses lseek() and fseek() to position within the file and the limit of the offset that the standard UNIX/POSIX seek library functions use are limited to 2GB. Informix's code always offsets from the beginning of the file not relative so the useable chunk (OFFSET + SIZE) is 2GB. On 64bit versions (I think the version letters start with H rather than the U for 32bit UNIX) the extended 64bit seek functions could be used and the chunk limit would be removed. You would have to upgrade Solaris AND IDS to 64bit versions to take advantage of this and I am not certain whether Informix has done this. For volume managers look to Veritas VM among others. Art S. Kagel