RE: ocfs2/oracleasm on Red Hat 4

  • From: "QuijadaReina, Julio C" <QuijadJC@xxxxxxxxxxxxxxx>
  • To: Matthew Zito <mzito@xxxxxxxxxxx>, "rprabha01@xxxxxxxxx" <rprabha01@xxxxxxxxx>
  • Date: Thu, 28 May 2009 14:53:04 -0400

Yes, I much rather use ASM to handle this kind of stuff for me.


From: Matthew Zito [mailto:mzito@xxxxxxxxxxx]
Sent: Thursday, May 28, 2009 12:46 PM
To: rprabha01@xxxxxxxxx; QuijadaReina, Julio C
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: ocfs2/oracleasm on Red Hat 4

Udev is nice, but it can be complicated to configure, and changes made on the 
storage array side can cause sudden and horrifying udev issues.  For example, 
by default udev uses scsi unique IDs as identifiers for individual devices.  If 
those IDs change, your device mappings will change, or cease to exist 

Udev definitely has its place, but nothing beats an application-level disk 
signature for guaranteeing consistency.


From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Rajeev Prabhakar
Sent: Thursday, May 28, 2009 12:06 PM
To: QuijadJC@xxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: ocfs2/oracleasm on Red Hat 4

Hello Julio,

There is always the "udev" option for device management. This means more work 
at the
sysadmins end.

On Thu, May 28, 2009 at 8:35 AM, QuijadaReina, Julio C 
<QuijadJC@xxxxxxxxxxxxxxx<mailto:QuijadJC@xxxxxxxxxxxxxxx>> wrote:
Thanks Alan,
What you say is interesting. We are a RAC shop and I have always used oracleasm 
tools to create/delete ASM disks for SAN shared storage before or after I use 
them for an ASM instance. Maybe it's just my ignorance, but is there another 
way to do that without oracleasm?

Other related posts: