When we were carving out our luns, we plaided them.
We made raid 10 across 6 disks, then stripped the logical volumes also.

Then, when we started carving out the luns, we realized that the first lun we made from each volume group, was the outer portion of the disk. The second lun was a little farther in and so on.
We decided that the disk would have faster access to the outer portions, so we put our busiest dbspaces in the first lun, and so on.









========================
-<<Floyd Wellershaus>>-
Database Administrator
Unix Administrator



email: fwellers@yahoo.com


Home: 703-430-0805


Cell: 703-477-6045
========================


http://www.one.org/



----- Original Message ----
From: Neil Truby <neil.truby@ardenta.com>
To: informix-list@iiug.org
Sent: Thursday, August 3, 2006 2:29:53 AM
Subject: Re: dbspaces design in SAN arrays


"Octavio Gomez" <sogomez@hotmail.com> wrote in message
news:mailman.121.1154561456.20706.informix-list@iiug.org...

>> Hi everyone,
>> I used to work with servers with a bunch of disks connected to them, so
>> it was relative easy to design dbspaces and tables fragmentation in that
>> scene.
... Is there any special consideration for dbspaces, chunks and tables
fragmentation design in SAN environments with dozens or hundreds of disks
inside of one array?

Don't waste time doing anything more than rudimentary placement planning.
The level of indirection between the LUNs presented to your host and the
physical disks is so high as to make the exercise worthless.


_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list