RE: ocfs2/oracleasm on Red Hat 4
- From: "Matthew Zito" <mzito@xxxxxxxxxxx>
- To: <rprabha01@xxxxxxxxx>, <QuijadJC@xxxxxxxxxxxxxxx>
- Date: Thu, 28 May 2009 12:45:52 -0400
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 altogether.
Udev definitely has its place, but nothing beats an application-level
disk signature for guaranteeing consistency.
Thanks,
Matt
________________________________
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.
-Rajeev
On Thu, May 28, 2009 at 8:35 AM, QuijadaReina, Julio C
<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:
