- 论坛徽章:
- 0
|
网上查到相关解释:
However, a local volume group has been incorrectly set up as clustered, and there isnot a cluster set up for the locking, when unset the cluster flag is attempted to be removed, vgchange will print out "Skipping cluster volume group."
In order to fix this, edit the /etc/lvm/lvm.conf file and set locking_type = 0. Then run the command vgchange -cn VolumeGroupName. After this, change the locking_type in the /etc/lvm/lvm.conf back to the original value.
我的操作方法:
[root@db etc]# vgscan
Reading all physical volumes. This may take a while...
Found volume group "data" using metadata type lvm2
Skipping clustered volume group db1
(可以看到一个cluster volume group: db1)
[root@db etc]# vgchange -cn online
Skipping clustered volume group online
(无法修改)
[root@db etc]# vi /etc/lvm/lvm.conf
(设置locking_type = 0)
[root@db etc]# vgchange -cn db1
WARNING: Locking disabled. Be careful! This could corrupt your metadata.
Volume group "db1" successfully changed
(修改db1成功)
[root@db etc]# vgscan
WARNING: Locking disabled. Be careful! This could corrupt your metadata.
Reading all physical volumes. This may take a while...
Found volume group "data" using metadata type lvm2
Found volume group "db1" using metadata type lvm2
(可以看到已经不是cluster volume group了) |
|