Bug 5761185

Related
KROWN-123009 [ASM] ファイルのリサイズに失敗すると領域が解放されない

Bug番号 5761185
登録済 13-JAN-2007 更新済 08-JUN-2007
製品 Oracle Server - Enterprise Edition 製品バージョン 10.2.0.2.0
プラットフォーム Linux x86-64 プラットフォーム・バージョン 2.4.21-47.ELSMP
データベース・バージョン 10.2.0.2.0 影響を受けるプラットフォーム Generic
重要度 Severe Loss of Service ステータス Development to Q/A
Base Bug N/A 修正された製品バージョン 10.2.0.99

問題の内容:

ORA-15041: DISKGROUP SPACE EXHAUSTED AFTER ADDING DISKS TO A DISKGROUP 
--------------------------------------------------------------------------------

*** 01/13/07 03:49 pm *** 
TAR: 
---- 
6084089.994 
. 
PROBLEM: 
-------- 
Some disks with larger capacity were added to each diskgroup (ARCHDG01 and  DATADG01).  
Both diskgroups failed during rebalance operation with error  
ORA-15041.
. 
. 
This is a 2 node RAC cluster.  All the commands were executed from instance  
ASM2 and instance ASM1 was closed during this operation. 
. 
The diskgroups were created with NORMAL redundancy but back in December, one  
failgroup was put offline because the storage was removed from the cluster. 
. 
. 
DIAGNOSTIC ANALYSIS: 
-------------------- 
asmdebug from note 351117.1  was provided and following is observed: 
. 
1. The disks added to each diskgroup are recognized, but they have all the  
space FREE     
   Check in asmdebug.out for this title: 'Number of allocated (V) and free  
(F) Allocation Units' 
. 
Example:  For diskgroup 2, 9 disks were added (0-8) , capacity of 52gb.  They  
have only 11 AU allocated which will be part of ASM Metadata. (rebalance  
failed).                      
. 
.         
    2          0 F      52405                                                    
    2          0 V          11                                                    
    2          1 F      52405                                                    
    2          1 V          11                                                    
    2          2 F      52405                                                    
    2          2 V          11                                                    
    2          3 F      52405                                                    
    2          3 V          11                                                    
    2          4 F      52405                                                    
    2          4 V          11                                                    
    2          5 F      52405                                                    
    2          5 V          11                                                    
    2          6 F      52405                                                    
    2          6 V          11                                                    
    2          7 F      52405                                                    
    2          7 V          11                                                    
    2          8 F      52405                                                    
    2          8 V          11                                            
. 
. 
2.  Error ora-15041 could be reported when there is a mismatch between disk  
directory (DD) structure and allocation tables.  DD is used by v$asm* views  
to obtain total_mb and free_mb columns.    It was verified that both  
structures report same data. 
. 
. 
. 
3.  There is not any bad allocation of a file.  All values under  
v$asm_file.space are exactly 2*v$asm_file.bytes which is the correct config.  
for normal redundancy. 
. 
It seems that one possible cause of the error could be the difference in the  
capacity of the disks.  While the old disks were between 17gb and 25gb, the  
new ones are 52gb.  
. 
WORKAROUND: 
----------- 
None.  Probably removing the new disks and add disks with capacity similar to  
the old disks. 
. 
There are different answers about the disk configuration.  Some indicate  
having disks with different capacity wont cause a problem because data will  
be allocated    base on the capacity of the disk.  
. 
. 
RELATED BUGS: 
------------- 
. 
REPRODUCIBILITY: 
---------------- 
two diskgroups were affected after following identical procedure. 
. 
TEST CASE: 
---------- 
. 
STACK TRACE: 
------------
. 
SUPPORTING INFORMATION: 
----------------------- 
. 
24 HOUR CONTACT INFORMATION FOR P1 BUGS: 
---------------------------------------- 
. 
DIAL-IN INFORMATION: 
-------------------- 
. 
IMPACT DATE: 
------------ 
.