Moving ROOTDBSPACE travails

I'm trying to physically move a client's rootdbs from a Unix file based dbs to a raw device. On the theory that the primary and mirror dbspaces are *exactly* the same (I have been told this by an Informix Engineer) I've tried turning mirroring on for the rootdbs, and created a mirror on a raw device. I brought Online down then brought it back up with the primary rootdbs symbolic link now pointing to the mirror slice. I turned mirroring off in the onconfig file so that Online wouldn't try to search for the mirror chunk. This did not work. Online complained about inconsistencies in the chunks. I'm curious why. But more importantly: Since that did not work, I'm going to try another way: I'll bring the primary chunk down (leaving a mirror up), I'll repoint the rootdbs symbolic link (formerly the primary) to a raw device, then bring it back online. This should recover the dbs in the raw device, NO?? Questions: 1) Assuming the above is viable, when I bring the former primary root chunk/dbs back online, does it become the mirror or does it revert back to being the primary chunk? 2) the primary rootdbs was created with an offset of 2000k. I don't suppose that when I recover it after dropping it that I can get rid of the offset (it's not needed)?? 3) When I mark the primary rootdbs (Unix file) as down, can I then *drop* it? This would make the mirror dbspace the primary (with no mirror) - then could I add another mirror, this time in a raw slice. (with no offset??) Anything I need to be warned about?. Is there is a better way to do this?? Am I about to do something foolish and regrettable? Cosmo Lee -- * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ADDRESS ALTERED TO FOIL SPAMMERS: Remove "*NO-SPAM*" to reply. Cosmo Lee Multi-User Computer Systems Brooklyn, NY "JUST SAY 'NO' TO SPAM" * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *