RE: Using Large Disks under Solaris

Define chunks of any size, but use offset and length when defining dbspaces, will that work ? depends on informix accepting offsets greater that 2GB. -----Original Message----- From: Paul watson [SMTP:watsop@russellcorp.co.uk] Sent: Tuesday, October 26, 1999 11:24 AM To: rich@airflash.com Cc: informix-list@iiug.org Subject: Re: Using Large Disks under Solaris Firstly you can have 8*2GB paritions, slices 0-7 inclusive, so you'd loose 2GB per disk. To use the whole disk you need some form of LVM, either DiskSuite (free with Solaris) or Veritas (you have to pay for it). Apart from cost element DiskSuite and Veritas have other differences. The main one being DiskSuite is more suited to smaller layouts and is still, AFAIK, restricted by the number of partitions on the disk, but is easy to use, easy to configure and provides adequate performance and if used on FSs then provides logging . Once you start getting into large disk sub-systems that have significant amounts of NVRAM then Veritas start to come into it's own. Paul Watson WF Software Ltd Tel: +44 1436 674729 Fax: +44 1436 678729 www.wfsoftware.com/informix # If you broke it, hide the evidence >>> Richard Auslander <rich@airflash.com> 10/25/99 08:27PM >>> Greetings all. Perhaps someone (besides Obnoxo) can help me with this? It would be greatly appreciated. I have observed that Informix has a chunk size limitation of around 2.01GB. In addition, on Solaris, we are able to define no more than 7 (and typically 6) partitions on a given hard disk. Although I am very aware of how to use 'onspaces' to combine multiple chunks into a single dataspace, it still appears that Informix under Solaris can support a maximum physical disk size of around (6 * 2.01 GB), which comes out to [I goed to colledge] around 12GB, assuming I *want* to make all the chunks the maximum of 2GB, which I often don't. We recently purchased a Sun E450, which we ordered with 18GB disks. In practive, I've been able to use only around 60-70% of the disk space purchased, and as disk densities increase, the problem will only worsen. Can someone pleeeez tell me that I'm wrong about this limit? ;-) Rich -- Richard C. Auslander Database Manager AirFlash, Inc. 1733 Woodside Rd., Suite #110 Redwood City, CA 94061 (650) 556-7928 www.airflash.com ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************

"M. Najaa" wrote: > > Define chunks of any size, but use offset and length when defining dbspaces, will that work ? depends on informix accepting offsets greater that 2GB. No it will not work. The combination OFFSET+SIZE may not exceed 2097150K so OFFSET itself cannot. Art S. Kagel

Yup, discovered this one the hard way, too. If an offset > 2097150K were possible, I'd have solved this already. ;-) "Art S. Kagel" wrote: > "M. Najaa" wrote: > > > > Define chunks of any size, but use offset and length when defining dbspaces, will that work ? depends on informix accepting offsets greater that 2GB. > > No it will not work. The combination OFFSET+SIZE may not exceed 2097150K > so OFFSET itself cannot. > > Art S. Kagel -- Richard C. Auslander Database Manager AirFlash, Inc. 1733 Woodside Rd., Suite #110 Redwood City, CA 94061 (650) 556-7928 www.airflash.com