I don't want to touch manually /etc/filesystems because my hand made changes will be overwritten when I exportvg/importvg...
It is necessary to remove the old fs/LV first if not it will complain during reimporting newVG that the mount point is used. And the mount point is storet in LVCB of new LV and it is the same as in old LV.
Maybe (I didn't check it) the other soulution would be the following:
1. edit /etc/filesystems - add new stanza for new FS build on new copy of LV (of course fjslog and mount point has to be another one)
2. made change of FS (smitty fs) to update the LVCB of the LV
And here is the information about LVCB:
The logical volume control block (LVCB) is the first 512 bytes of a logical volume. This area holds important information such as the creation date of the logical volume, information about mirrored copies, and possible mount points in the journaled filesystem (JFS). Certain LVM commands are required to update the LVCB, as part of the algorithms in LVM. The old LVCB is read and analyzed to see if it is a valid. If the information is valid LVCB information, the LVCB is updated. If the information is not valid, the LVCB update is not performed and the user is given the warning message:
Warning, cannot write lv control block
data.
Most of the time, this is a result of database programs accessing raw logical volumes (and bypassing the JFS) as storage media. When this occurs, the information for the database is literally written over the LVCB. Although this may seem fatal, it is not the case. Once the LVCB is overwritten, the user can still:
Expand a logical volume
Create mirrored copies of the logical volume
Remove the logical volume
Create a journaled filesystem to mount the logical volume
There are limitations to deleting LVCBs. The logical volumes with deleted LVCB's face possible, incomplete importation into other AIX systems. During an importvg, the LVM command will scan the LVCB's of all defined logical volumes in a volume group for information concerning the logical volumes. If the LVCB is deleted, the imported volume group will still define the logical volume to the new AIX system, which, is accessing this volume group, and the user can still access the raw logical volume. However, any journaled filesystem information is lost and the associated mount point won't be imported into the new AIX system. The user must create new mount points and the availability of previous data stored in the filesystem is not assured. Also, During this import of logical volume with an erased LVCB, some non-jfs information concerning the logical volume, which is displayed by the lslv command, cannot be found. When this occurs, the system uses default logical volume information to populate the logical volume's ODM information. Thus, some output from lslv will be inconsistent with the real logical volume. If any logical volume copies still exist on the original disks, the information will not be correctly reflected in the ODM database. The user should use the rmlvcopy and mklvcopy commands to rebuild any logical volume copies and synchronize the ODM.
regards,
Chris
