vgchange -c y後的【Skipping clustered volume group 】
環境介紹:
oracle RED HAT 5.6 32bit
LVM
vgchange -c y /dev/oracle_vm
[@more@]在對LVM group做了cluster設定後,想要更新都報:
Skipping clustered volume group oracle_vm
[root@qqovm ~]# vgdisplay /dev/oracle_vm
Skipping clustered volume group oracle_vm
[root@qqovm ~]# vgchange -c n /dev/oracle_vm
Skipping clustered volume group oracle_vm
[root@qqovm ~]# vgchange -a n /dev/oracle_vm
Skipping clustered volume group oracle_vm
[root@qqovm ~]#
解決辦法是設定lvm.conf檔案內的locking_type 由1設定為0:
[root@qqovm ~]# more /etc/lvm/lvm.conf |grep locking
# Type of locking to use. Defaults to local file-based locking (1).
# Turn locking off by setting to 0 (dangerous: risks metadata corruption
# Type 2 uses the external shared library locking_library.
# Type 3 uses built-in clustered locking.
locking_type = 1
# If using external locking (type 2) and initialisation fails,
# clustered locking.
# If you are using a customised locking_library you should set this to 0.
fallback_to_clustered_locking = 1
# If an attempt to initialise type 2 or type 3 locking failed, perhaps
# to 1 an attempt will be made to use local file-based locking (type 1).
fallback_to_local_locking = 1
locking_dir = "/var/lock/lvm"
# The external locking library to load if locking_type is set to 2.
# locking_library = "liblvm2clusterlock.so"
[root@qqovm ~]#
[root@qqovm ~]# more /etc/lvm/lvm.conf |grep locking
# Type of locking to use. Defaults to local file-based locking (1).
# Turn locking off by setting to 0 (dangerous: risks metadata corruption
# Type 2 uses the external shared library locking_library.
# Type 3 uses built-in clustered locking.
locking_type = 0
# If using external locking (type 2) and initialisation fails,
# clustered locking.
# If you are using a customised locking_library you should set this to 0.
fallback_to_clustered_locking = 1
# If an attempt to initialise type 2 or type 3 locking failed, perhaps
# to 1 an attempt will be made to use local file-based locking (type 1).
fallback_to_local_locking = 1
locking_dir = "/var/lock/lvm"
# The external locking library to load if locking_type is set to 2.
# locking_library = "liblvm2clusterlock.so"
[root@qqovm ~]#
[root@qqovm ~]# vgchange -c n /dev/oracle_vm
WARNING: Locking disabled. Be careful! This could corrupt your metadata.
Volume group "oracle_vm" successfully changed
修改完後再將屬性改回去:
[root@qqovm ~]# more /etc/lvm/lvm.conf |grep locking
# Type of locking to use. Defaults to local file-based locking (1).
# Turn locking off by setting to 0 (dangerous: risks metadata corruption
# Type 2 uses the external shared library locking_library.
# Type 3 uses built-in clustered locking.
locking_type = 1
# If using external locking (type 2) and initialisation fails,
# clustered locking.
# If you are using a customised locking_library you should set this to 0.
fallback_to_clustered_locking = 1
# If an attempt to initialise type 2 or type 3 locking failed, perhaps
# to 1 an attempt will be made to use local file-based locking (type 1).
fallback_to_local_locking = 1
locking_dir = "/var/lock/lvm"
# The external locking library to load if locking_type is set to 2.
# locking_library = "liblvm2clusterlock.so"
[root@qqovm ~]#
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/10130206/viewspace-1049411/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- [HP-UX] ERROR: Function activate_volume_groupUXErrorFunction
- Clustered Index Scan and Clustered Index SeekIndex
- Skipping
- ERROR: The LVM time stamp for shared volume group: datavg is inconsistentErrorLVM
- D. Skipping
- vgchange指令:修改卷組屬性GC
- SQL247 按照dept_no進行彙總(group_concat(X,Y))SQL
- clientX/Y pageX/Y offsetX/Y layerX/Y screenX/Y clientHeight innerWidth...client
- Snapkit,呼叫layoutIfNeeded後x、y為負數。APK
- 1152:最大數max(x,y,z)(C C++)C++
- C/C++ Y/N 重複輸入功能實現C++
- 資料庫表--index clustered table資料庫Index
- 資料庫表--hash clustered table資料庫
- Availability Group On Linux 搭建後記AILinux
- Docker VolumeDocker
- [HP-UX] vgchange -a e -q n vgxxx --執行此命令後,啟用巻組UXGC
- 資料庫表--sorted hash clustered table資料庫
- sql中的left切割 與 group by後的兩次分組SQL
- lun跟volume的區別
- Flocker 做為後端儲存代理 docker volume-driver 支援後端Docker
- Linux升級核心後報No volume groups found錯誤Linux
- 簇表及簇表管理(Index clustered tables)Index
- Understanding HTTP plug-in failover in a clustered environmentHTTPAI
- docker建立volume 指定volume 匯出image 匯入imageDocker
- C/C++—— 輸入兩點座標(X1,Y1),(X2,Y2),計算並輸出兩點間的距離C++
- 『指數a,b,c,d無上下限:X+Y+Z=1的恆等式』恆等式
- 資料庫的sort group by和hash group by資料庫
- Docker Volume介紹Docker
- Oracle ASM Volume DirectoryOracleASM
- Clustered Shading架構實現步驟架構
- ROUND(x,y)與TRUNC(x,y)函式中y引數值為省略、空值與null的區別函式Null
- kubernetes概念之六:Volume&Persistent Volume&Namespace&Annotationnamespace
- Python中x=y與x==y的區別。(比較簡單)Python
- 什麼是Clustered Table,與其他型別的table有何不同型別
- 理解exp, imp 使用direct=y 及imp commit=yMIT
- 翻譯(九)——Clustered Indexes: Stairway to SQL Server Indexes Level 3IndexAISQLServer
- 四、有一行電文,已按下面規律譯成密碼:A-->Z B-->Y C-->X a-->z b-->y c-->x...密碼
- k8s-volumeK8S