Logical Volume problems

[Sunny Jaisinghani]

Gary,

check the file system in the LV using fstyp. If the File system is already created then there is no need to do newfs.

doing newfs will destroy your data.

[Gary L]

Thanks, sunny

the file system already exist, no need to newfs, thanks again

have a great day

[Denver Osborn]

After importing, the "lvol1" was your missing "lvsys8" volume. When using vgimport it checked the lvm data and determined that there were existing lvols. When importing the vg using a map file, the lvols are assigned names based on the contents of your map file. Since the map file didn't contain "1 lvsys8" the import assigned it the generic lvol1 name.

You're fine to rename the lvol1 and rlvol1 device special file after the import.

The only thing you may have done different is to have looked at lvol1 (lvsys8) before deciding to newfs. Running 'fstyp -v /dev/vg08/rlvsys8' would show specs about the filesystem type had there been one. If it came back w/ details about a filesystem, then mounting it or using fsck as needed would've been your next step.

Anyhow, looks like you've got things where you need them to be.

-denver

[Gary L]

thanks Denver

what is the safety way to rename a logic volume lvsys8 and rlvsys8, ditectly use "mv"
# mv lvol1 lvsys8
# mv rlvol1 rlvsys8 ?

thx
-Gary

[Denver Osborn]

Yup, that's what I'd do. Unmount it if it's mounted, then 'mv lvol1 lvsys8' and 'mv rlvol1 rlvsys8'. If you'd added it to the /etc/fstab before renaming, of course you'll need to update the fstab entry too.

-denver

[Gary L]

got it, thx denver
hava a great day

-Gary