[Oracleasm-users] Oracle ASMLib and IBM SDD

[Sheridan, Matt]

We're trying something similar. We have IBM x335's connected to an ESS
(Shark) 750. We're running Red Hat ES 3.0 Update 4 and IBM's SDD. We
were getting the same "Device <blah> is not a partition" when trying to
run oracleasm createdisk. We found a way past that. It's kludgy, but
seems to work. We ran the createdisk command using the underlying sd
(ie. /dev/sdd1) instead of the vpath (ie. /dev/vpatha1). That created
the asm VOL# successfully. We then set the ORACLEASM_SCANORDER parameter
in /etc/sysconfig/oracleasm to "vpath sd" so the vpath would be picked
up and used upon reboot. After rebooting, an oracleasm querydisk of that
disk shows it using the major/minor #'s for the vpath instead of the sd.
 
BUT, when we then try to create a diskgroup in our ASM instance using
that disk (ORCL:VOL1 and another one VOL2), we get:
 
SQL> create diskgroup dgroup1 external redundancy disk 'ORCL:VOL*';
create diskgroup dgroup1 external redundancy disk 'ORCL:VOL*'
*
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15186: ASMLIB error function = [asm_io],  error = [3],  mesg = [I/O
Error]
ORA-15186: ASMLIB error function = [asm_io],  error = [3],  mesg = [I/O
Error]

Could we be hitting another GETGEO issue, just in a different section of
the code? Any way to strace the sqlplus command to verify this?
(Joel/Heath: did you ever find a fix for your error?)
 
P.S. If it helps, we get a slightly different error if we try the above
"create diskgroup" command a second time:
 
SQL> create diskgroup dgroup1 external redundancy disk 'ORCL:VOL*';
create diskgroup dgroup1 external redundancy disk 'ORCL:VOL*'
*
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-00600: internal error code, arguments: [kfgrpJoin2], [5], [], [],
[], [], [], []
ORA-15186: ASMLIB error function = [asm_io],  error = [3],  mesg = [I/O
Error]
ORA-15186: ASMLIB error function = [asm_io],  error = [3],  mesg = [I/O
Error]
 
Matt
On Fri, Jun 03, 2005 at 07:43:42PM -0500, heath seals wrote:

> I'm seeing these calls to ioctl :

> 

> 28040 ioctl(4, 0x4c05, 0xfeff9130)      = -1 EINVAL (Invalid argument)

> 28040 ioctl(4, 0x4c03, 0xfeff9130)      = -1 EINVAL (Invalid argument)

> 28040 ioctl(4, 0x301, 0xfeff9530)       = -1 EINVAL (Invalid argument)



	Tada.  0x4c05 = LOOP_GET_STATUS64, 0x4c03 = LOOP_GET_STATUS, and

0x301 is HDIO_GETGEO.  Since the IBM driver does not support GETGEO,

ASMLib cannot determine whether it is a partition or not.  IBM needs to

fix that.



Joel
 
 
Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/oracleasm-users/attachments/20050628/cc87a815/attachment.html