114网址导航VxVM报错“Some volumes in the disk group are in use”的原因和解决方法
运维派推荐
运维派问答社区是专注于IT运维领域的学习、交流、互助的平台，这是属于IT运维人自己的技术社区。
> VxVM报错“Some volumes in the disk group are in use”的原因和解决方法
1群： - 运维综合
2群： - 运维综合
3群：1689067
- Linux Shell脚本
微信：yunweipai（或扫描以下二维码）
在使用SYMANTEC的VxVM卷管理软件时，执行vxdg deport磁盘组(disk group)时报错“Some volumes in the disk group are in use”，形如：
# vxdg deport testdg
VxVM vxdg ERROR V-5-1-584 Disk group testdg: Some volumes in the disk group are in use
据SYMANTEC官方描述，该问题在VxVM 5.1以下才存在“This issue is applicable to systems running VxVM less than 5.1 version.”，但实际验证中发现，在该版本依然存在该问题。
vxdg deport命令的作用是卸载磁盘组(disk group)，其前提要求是磁盘组内的卷已经没有I/O（若是文件系统，就需要先umount该文件系统卷；若是裸设备，则需要停止应用该设备的应用）。但在已经umount该磁盘组的文件系统卷的情况下，还是遇到了无法卸载磁盘组并出现上述的错误信息。
可以通过以下命令检查VxVM卷是否有I/O操作：
# vxprint -g
-m | grep devopen
若回显信息中包含“devopen=on”，则表示该卷在内核中依然处于使用状态，只是用df -k之类的命令无法查看而已。
SYMANTEC官方给的解决方法是——重启该操作系统，原文描述是“Only way to resolve the issue is to reboot the system.”
转载请注明： &
与《VxVM报错“Some volumes in the disk group are in use”的原因和解决方法》相关的文章.
长微博分享
博主暂未提供此篇文章的长微博，请联系站长。
二维码分享
打开微信（或者其他社交APP），选择“发现”，进入“扫一扫”拍摄即可。博客访问： 496008
博文数量： 227
注册时间：
IT168企业级官微
微信号：IT168qiye
系统架构师大会
微信号：SACC2013
分类： Linux
In this Document
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.2 - Release: 10.2 to 11.2Information in this document applies to any platform.
V$ASM_DISK view shows some disk header status as IGNORED and group number as "0".
This is not a mormal situation but can happen in the following senario.1.
If there are more than 2 disks dropped forcefully from the same
diskgroup created with normal redundancy while the diskgroup is still
mounted, these disks still show "MEMBER" and group number as "0".
a new disk is added to the diskgroup or existing disks are added in
different order, there is a possibility that the same disk number and
disk name can be assigned to the ones that was assigned to one of
dropped disks which has not been added yet. This situation can happen either when one of SAN failgroup crash or when one of cell node from Exadata crash.2.
In RAC environment, ASM disk added to a existing diskgroup should be
seen from all nodes. If one of nodes doesn't see the disk being added,
the operation will fail with "ORA-15075 disk(s) are not visible
cluster-wide"
but the disk being added keeps the new disk number and
disk name showing "MEMBER" status.
After this, a new disk is added to
the RAC node successfully, chances are the new disk gets the same disk
number and diskname with the one that was failed in the first place.The following similar error occurs when these disks showing IGNORED status are attempted to be added an existing diskgroup.
SQL> alter diskgroup data add failgroup F2 disk '/dev/oracleasm/disks/ASM1' ;alter diskgroup data add failgroup F2 disk '/dev/oracleasm/disks/ASM1'*ERROR at line 1:ORA-15032: not all alterations performedORA-15033: disk '/dev/oracleasm/disks/ASM1' belongs to diskgroup "DATA"
IGNORED status can be seen for
ASM disks which are not part of any
currently mounted diskgroup but it shows the same disk header
information with one of disks that are currently mounted such as disk
number, disk name and diskgroup and the status as "MEMBER" and group
number as "0".
Please see how to check whether there are at
ASM disks showing the same disk header information in Appendix 1
below using kfed.1. When the diskgroup from which the disk has
been dropped is currently mounted, try to add the disk showing "IGNORED"
status using force option to the original diskgroup from which the disk
has been dropped.
Please see
- for details how to add a disk back to the original diskgroup.Example)
SQL> alter diskgroup data add failgroup F2 disk '/dev/oracleasm/disks/ASM1'Diskgroup altered2.
When the diskgroup from which the disk has been dropped is not
currrently mounted, v$asm_disk shows the correct disk as MEMBER by
comparing creation time from disk directory .
If a disk showing the
same disk number and has a different creation time from disk directory,
the status is seen as IGNORED.
example) ASM1 and ASM2 show the same disk header information from kfed output.
SQL>@diskifno G_N
M_STATU H_STATUS
MO_STAT STATE
M_DATE---- ---- ----------- ---------- ------- ---------- ------- -------- ------------------------- --------------------
/dev/oracleasm/disks/ASM2
IGNORED MEMBER
/dev/oracleasm/disks/ASM1
/dev/oracleasm/disks/ASM4
/dev/oracleasm/disks/ASM3
0 PLAY_0000
/dev/oracleasm/disks/ASM5
0 KYLE_0000
/dev/oracleasm/disks/ASM6
20:52:442-1.
ASM discards the disk showing IGNORED status automatically by comparing
creation time from disk directory
when mounting DATA diskgroup.
SQL> alter dDiskgroup altered.Please note that ASM1 has been excluded from DATA diskgroup.
SQL> @diskinfo G_N
M_STATU H_STATUS
MO_STAT STATE
M_DATE---- ---- ----------- ---------- ------- ---------- ------- -------- ------------------------- --------------------
IGNORED MEMBER
/dev/oracleasm/disks/ASM1
0 PLAY_0000
/dev/oracleasm/disks/ASM5
0 DATA_0000
/dev/oracleasm/disks/ASM2
1 DATA_0001
/dev/oracleasm/disks/ASM4
2 DATA_0002
/dev/oracleasm/disks/ASM3
0 KYLE_0000
/dev/oracleasm/disks/ASM6
20:52:442-2. And then the disk showing IGNORED can be added using step 1.Appendix1. How to check whether there are duplication disks showing
the same disk header information.
- Check whether kfed executable exist in your
- Rebuild if kfed executable doesn't exist using the following way.&&
$cd $ORACLE_HOME/rdbms/lib&&
$make -f ins_rdbms.mk ikfed
- Take a kfed output for the disks. If the following information of
the header is the same, the 2 disks are considered to be the same.
Please note mntstmp.hi and mntstmp.lo (disk mount time) can be different to be the same disk in this excercise.
$ kfed read /dev/oracleasm/disks/ASM1 | egrep 'dsknum|dskname|grpname|fgname|hdrsts|mntstmp.hi|mntstmp.lo'
References
- How To Add Back An ASM Disk or Failgroup (Normal or High Redundancy)
After A Transient Failure Occurred (11.1 & 10.2) Or
DISK_REPAIR_TIME Attribute Expired (10.1 & 11.2)?
阅读(6173) | 评论(0) | 转发(0) |
相关热门文章
给主人留下些什么吧！~~
请登录后评论。