Re: ASM not discovering disks after workaround for bug 6605620
- From: TESTAJ3@xxxxxxxxxxxxxx
- To: sacrophyte@xxxxxxxxx
- Date: Thu, 19 Mar 2009 14:11:31 -0400
We just went through this, and there is a document on EMC website i think
about having to start the disk partition beyond the 1M part, some
performance issue. I doubt thats it, but what we had to do was make sure
we did a delete disk and create disk on the "disk partition" name.
joe
_______________________________________
Joe Testa, Oracle Certified Professional
Senior Consultant
Data Engineering and Administration
Nationwide Investments
(Work) 614-677-1668
(Cell) 614-312-6715
Interested in helping out your marriage?
Ask me about "Weekend to Remember"
Dec 11-13, 2009 here in Columbus.
From:
Charles Schultz <sacrophyte@xxxxxxxxx>
To:
TESTAJ3@xxxxxxxxxxxxxx
Cc:
"oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>,
oracle-l-bounce@xxxxxxxxxxxxx
Date:
03/19/2009 01:46 PM
Subject:
Re: ASM not discovering disks after workaround for bug 6605620
Sent by:
oracle-l-bounce@xxxxxxxxxxxxx
It is, but thanks for uncovering all the stones. =)
Progression of tasks:
/sbin/powermt config
/etc/init.d/oracleasm createdisk VOLUME5 /dev/emcpoweri
Marking disk "VOLUME5" as an ASM disk: [FAILED]
/usr/sbin/asmtool -C -l /dev/oracleasm -n VOLUME5 -s /dev/emcpoweri -a
force=yes
asmtool: Device "/dev/emcpoweri" is not a partition
asmtool: Continuing anyway
<urbdb1> /u01/app/oracle/admin/+ASM/bdump: ll /dev/oracleasm/disks/
total 0
drwxr-xr-x 1 root root 0 Mar 19 11:45 .
drwxr-xr-x 4 root root 0 Mar 9 02:36 ..
brw-rw---- 1 oracle dba 120, 32 Mar 9 02:36 VOLUME1
brw-rw---- 1 oracle dba 120, 16 Mar 9 02:36 VOLUME2
brw-rw---- 1 oracle dba 120, 48 Mar 9 02:36 VOLUME3
brw-rw---- 1 oracle dba 120, 96 Mar 9 02:36 VOLUME4
brw-r----- 1 root root 120, 128 Mar 19 11:46 VOLUME5
As you can see, VOLUME5 has the wrong permissions. I fixed that - ASM now
discovers the disks. Woohoo. However, I cannot add it to the diskgroup. I
am thinking that is a more trivial issue. Thanks again for asking the
obvious and helping me look again. =)
On Thu, Mar 19, 2009 at 12:16 PM, <TESTAJ3@xxxxxxxxxxxxxx> wrote:
Have you looked to see if its in /dev/oracleasm/disks yet?
Can I assume you did the oracleasm createdisk to mark it as asm disk(I
know i'm stating the obvious to you but someone else might benefit) :P
joe
_______________________________________
Joe Testa, Oracle Certified Professional
Senior Consultant
Data Engineering and Administration
Nationwide Investments
(Work) 614-677-1668
(Cell) 614-312-6715
Interested in helping out your marriage?
Ask me about "Weekend to Remember"
Dec 11-13, 2009 here in Columbus.
From:
Charles Schultz <sacrophyte@xxxxxxxxx>
To:
"oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
Date:
03/19/2009 01:12 PM
Subject:
ASM not discovering disks after workaround for bug 6605620
Sent by:
oracle-l-bounce@xxxxxxxxxxxxx
Today is our lucky day. =)
We attempted to add a new LUN to our 11.1.0.7 ASM, only to find that ASM
no longer talks "properly" to our version of EMC. I am a bit miffed that
Oracle thinks the problem is with EMC and has dismissed the bug from 2007.
But, that aside. We forced the disk to be added with asmtool, however ASM
does not discover the new disk. There are no relevant error messages in
the alert.log. So... how do we add this disk to a diskgroup? The disk is
named using the exact same formats that 4 pre-existing disks have (and
which are in active use by ASM), and I know it is not an issue with
asm_diskstring.
For those who are interested, the SRs are:
7486153.992
7486052.992
--
Charles Schultz
--
Charles Schultz
Sent from: Champaign Illinois United States.
Other related posts:
