> the main sticking point for this is if you had an older version of VxVM > (usually < 3.0) that you have continued to upgrade over the years. Along > the way, Veritas has increased the size of the private region to > accommodate more 'objects'. If you have: > * totally full disks (every sector/cylinder in use) > * a disk that was originally initialized in a very olf VxVM > configuration > * you are reusing it in a newer version > > Then you run into the potential that when you use vxdiskadm to replace a > failed or removed disk, that all the data will not fit with the new > private region size. In this cases, you can run vxdisksetup by hand and > use old_layout. In any other case I am aware of, using the default is > fine.
The 'old_layout' option is available in 3.x releases that require it. Beginning with 4.x, they appear to have renamed it 'noreserve'. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
