RE: Clusterware - identifying devices

  • From: "Amaral, Rui" <Rui.Amaral@xxxxxxxxxxxxxxxx>
  • To: 'LS Cheng' <exriscer@xxxxxxxxx>
  • Date: Mon, 21 Mar 2011 08:14:44 -0400

If you are doing it manually correct. You can script it using a high enough 
minor number as to not conflict with other devices of the same type.

From: LS Cheng [mailto:exriscer@xxxxxxxxx]
Sent: Monday, March 21, 2011 8:08 AM
To: Amaral, Rui
Cc: Freek.DHooge@xxxxxxxxx; avramil@xxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: Clusterware - identifying devices

So does that mean that mknod devices are not persistent?

On Mon, Mar 21, 2011 at 1:00 PM, Amaral, Rui 
<Rui.Amaral@xxxxxxxxxxxxxxxx<mailto:Rui.Amaral@xxxxxxxxxxxxxxxx>> wrote:
Major numbers are specific to the device type and shouldn't change on a reboot. 
Minors are dynamically allocated to the devices and can change on reboot after 

From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx> 
[mailto:oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>] On 
Behalf Of LS Cheng
Sent: Monday, March 21, 2011 5:52 AM
To: Freek.DHooge@xxxxxxxxx<mailto:Freek.DHooge@xxxxxxxxx>
Cc: avramil@xxxxxxxxxxxxxx<mailto:avramil@xxxxxxxxxxxxxx>; 
Subject: Re: Clusterware - identifying devices

Just wondering, can major and minor number change when the storage is 
reconfigured? For example addking new disks or remove and readd?

I am asking because mknod relies on minor and major numbers, would like to know 
if these number are persistent even after storage reconfiguration.


On Fri, Mar 18, 2011 at 3:57 PM, D'Hooge Freek 
<Freek.DHooge@xxxxxxxxx<mailto:Freek.DHooge@xxxxxxxxx>> wrote:
Most of the time I use mknod to create character devices (which I can name) 
from the disks and modify the asm_disktring parameter to look at the directory 
holding the character devices.

Freek D'Hooge
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx<mailto:freek.dhooge@xxxxxxxxx>
tel +32(0)3 451 23 82<tel:%2B32%280%293%20451%2023%2082>

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx> 
[mailto:oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>] On 
Behalf Of Lou Avrami
Sent: vrijdag 18 maart 2011 15:34
To: oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>
Subject: Clusterware - identifying devices

Hello all,

I've encountered a challenge installing RAC on a NetApp FiberSan.  I 
thought I would run it by oracle-l and see if anyone might have a solution.

I was doing an advanced installation of RAC on a 2-node Solaris 10 
configuration.  This is for a data warehouse application for a vendor, with 80 
TBs of storage for the database.

I start the installer, input the SCAN address, set up the virtual IPs and SSH 
connectivity, then come to the "Create ASM Disk Group" screen.  The top of the 
screen populates the name of the disk group as DATA, there are radio buttons 
for redundancy, then there is a box with all of the devices under /dev/rdsk, 
with checkboxes to the left.  It looks like there are at least 6 screens of 
these devices.  The list looks like this:

             Device                                   Size MB
- /dev/rdsk/c10t60A98000486E6476575A62584A594C66d0s2   2091473
- /dev/rdsk/c10t60A98000486E6476575A62584A612D76d0s2   2097152

I have a list of devices and what disk groups I want to assign them to ... but 
trying to pick device names out of a list of dozens like the ones above in an 
X-Windows screen is proving to be just about impossible.

Any ideas would be greatly appreciated.
Should I be looking at a response file?  I've never used a response file for a 
Clusterware installation.

Lou Avrami


NOTICE: Confidential message which may be privileged. Unauthorized 
use/disclosure prohibited. If received in error, please go to<> for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié. 
Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière 
d'aller au<> 
pour des instructions.

Other related posts: