It is a new mount point..
Okay here is what happened:
1. Created a new VG ==> oraclevg6
2. cplv logical volume from oldvg to newvg ( and the system created lv called fslv06 )
3. after the cplv was over lsvg -l oraclevg6 ==> showed that there is a log logical volume called loglv01
4. create a filesystem with a new name and not the existing one for the copied logical_volume call it /u06
5. mount /u06 on fslv06
6. doesn't work...umount /u06
7. logform /dev/loglv01
8. mount /u06
still no data present.
==========
Quote:
BTW - if you only want to move to new SAN - but not necessarily to a new volumegroup - why dont you just add the new disks to the existing VG and do a migratepv olddisk newdisk(s) and drop the old empty disks afterwards from the VG. This is for sure not the fastest but the easiest way as it doesnt need ANY downtime whatsoever.
No, it cannot be done for various administrative reasons.
1. the array is different and new san is different
2. Database team want to have the new disks totally seperate.
3. the above experiment was with 200GB and it took 3.5 - 4 hours....what about 2.6TB...... ? and if something goes wrong then the company application might need a total restore.
too risky !