Re: Cooked File system question

Sun locate devices during boot time and assign logical & physical names to them. If you add a new controller, there is a big chance this device naming will change (device tree) and you will miss up all chunks path names and engine will fail to start up. To avoid such a problem, you must have links to your chunks, so the paths can be re-constructed by only changing the link path to the new solaris disk slices names. -----Original Message----- From: Don Bryant <dsbryant@worldnet.att.net> To: informix-list@iiug.org <informix-list@iiug.org> Date: Tuesday, February 01, 2000 12:32 AM Subject: Cooked File system question >My site is using Informix DWS v.7.3 on a Sun 3000 running Solaris 2.6. Our >data is stored on an A5000 disk array with 14 drives. We are considering >upgrading the SCSI controllers so that we can have redundancy to that device >in case one channel (controller or GPIC) is lost. > >Not all of the chunks were created using symbolic links. I know that the >Admin manuals speak of using only symbolic links for raw file systems in >the case of controller failure or other hardware changes. Does this appy >equally to cooked file systems? > >In other words if I change the drive controller configuration will the >Informix engine still se my chunks/extents? > >Thanks, > >Don Bryant >