RE: ASM bug?
- From: "Dimensional DBA" <dimensional.dba@xxxxxxxxxxx>
- To: <maureen.english@xxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 1 Oct 2014 17:27:39 -0700
What Multipathing SW are you using?
Matthew Parker
Chief Technologist
425-891-7934 (cell)
Dimensional.dba@xxxxxxxxxxx
View Matthew Parker's profile on LinkedIn
-----Original Message-----
From: Dimensional DBA [mailto:dimensional.dba@xxxxxxxxxxx]
Sent: Wednesday, October 01, 2014 5:23 PM
To: 'maureen.english@xxxxxxxxxx'; 'oracle-l@xxxxxxxxxxxxx'
Subject: RE: ASM bug?
Did you put the disk id's in the multipath.conf file which hard sets the
mapping?
Matthew Parker
Chief Technologist
425-891-7934 (cell)
Dimensional.dba@xxxxxxxxxxx
View Matthew Parker's profile on LinkedIn
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Maureen English
Sent: Wednesday, October 01, 2014 4:44 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: ASM bug?
We're building a new system and the sysadmin and dba working on it
discovered a problem.
This is RHEL5 and Oracle 11.2.0.4 RAC.
> At boot, or when instructed to do so, Oracle ASM scans disks and
> creates an index of which ASM labels are on which disks, however it
> does not do anything to tell the kernel that it intends to use the disks
it has identified. It is not until ASM mounts the disks in a diskgroup that
it marks them as "in use".
>
> Until a disk is actually in use (opened), the kernel will happily
> unmap or re-map dm devices that Oracle ASM has already scanned. Oracle
> ASM will try to modify the wrong disk if the kernel remaps an unused dm
device to a different disk before ASM mounts it.
>
> When multipath is run with the -F option, it will flush all multipath
> devices that are not in use. When multipath re-maps the devices, it
> may assign different device numbers to the disks it flushed. There is
> no way to tell Oracle ASM to forget about a label it has scanned
> without deleting the ASM labels off the disk or rebooting the system. It
is very important not to flush a disk that ASM has already identified. Do
not use multipath -F if there are any unmounted ASM disks presented to the
system.
Is this a known bug, or are there some rules regarding ASM and multipath
that we missed?
I'm not actually working on this system, but thought it sounds like
something others would have encountered. I'm still searching through
Metalink docs....
- Maureen
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
