在操作系统为CentOS 7.8的环境上安装GI时，运行脚本报错：
ASM created and started successfully.
Disk Group VOTE mounted successfully.
clscfg: -install mode specified
clscfg: EXISTING configuration version 5 detected.
clscfg: version 5 is 11g Release 2.
Successfully accumulated necessary OCR keys.
clscfg: Arguments check out successfully.
NO KEYS WERE WRITTEN. Supply -force parameter to override.
-force is destructive and will destroy any previous cluster
configuration.
Failed to create voting files on disk group VOTE.
Change to configuration failed, but was successfully rolled back.
CRS-4000: Command Replace failed, or completed with errors.
Voting file add failed


查看日志有这样的提示：ORA-15303: Voting files could not be created in diskgroup VOTE due to small Allocation Unit size
查看仲裁盘块大小，发现问题：
[root@test1 queue]# more *block_size
::::::::::::::
logical_block_size
::::::::::::::
512
::::::::::::::
physical_block_size
::::::::::::::
4096




究其原因是它表现出不同的逻辑和物理块大小。对于大多数的情况下，物理和逻辑块的大小是相同的“512”。
查询ORACLE的官方网站，给出的解决方案是：


1. Oracle bug 11780656 is already fixed in 11.2.0.3 with compatible.asm = 11.2.0.3 but OUI does not allow to specify "compatible.asm" attribute to create OCRVOTE diskgroup.


   - Bug 11780656  - ASM MANAGED VOTING FILES CANNOT BE MORE THAN 64X AU SIZE






2. Oracle bug 13999609 indicates that ASMLib driver only works with the expectation that logical block size and physical block size are 512/512 bytes.   


   - Bug 13999609  - PHYSICAL BLOCK SIZE REPORTED CAN CAUSE ISSUES WITH 10G DATABASES
SOLUTION






1] Possible workaround is to use '/dev/oracleasm/disks/*' path instead of "ORCL:*" when creating OCRVOTE diskgroup in OUI.


OR


2] Install the new “oracleasm-support-2.1.8-1” ASMLIB RPM package (which contains the permanent fix) as described in note 1500460.1






根据以上提示，我们可以在安装oracleasm-support-2.1.8-1的包，或者也可以在选择ASM盘时，改用


/dev/oracleasm/disks/*的路径来解决此问题。


若根据上述方法进行处理还是没能解决。建议查看是否是使用的NETAPP存储，NETAPP的官网有此问题的CASE案例。给出如下解决方案：


For details and caveats regarding this workaround, see the Oracle Alert.


Additionally, Oracle has provided a patch and configuration parameter to enable ASMlib to continue to function using the correct logical block size.


# ORACLEASM_USE_LOGICAL_BLOCK_SIZE: 'true' means use the logical block size
# reported by the underlying disk instead of the physical. The default
# is 'false'
NetApp has also provided a workaround in versions 8.0.5, 8.1.3 and 8.2 of Data ONTAP 7-Mode. The workaround allows specified LUNs to continue to not report the logical blocks per physical block value. This work around should only be applied to LUNs used by Oracle ASMlib with the symptoms described in this article.


From the Data ONTAP 7-Mode CLI, enter the following commands:






> lun set report-physical-size <path> disable（netapp存储设置）

进入/etc/sysconfig目录，修改其下的oracleasm文件，将其中的

[oracle@rac1 ~]$ cat /etc/sysconfig/oracleasm

...

# ORACLEASM_USE_LOGICAL_BLOCK_SIZE: 'true' means use the logical block size

# reported by the underlying disk instead of the physical. The default

 

# is 'false'

 

ORACLEASM_USE_LOGICAL_BLOCK_SIZE=false

将ORACLEASM_USE_LOGICAL_BLOCK_SIZE=false改为true，并对应修改NETAPP上的存储设置参数