Block Device Mapping

I'm been given a driver that is 90% complete.
It is 'block' device that can support many partitions. It is identified as a 'scsi' device even though it does not remotely look like a scsi device.
Currently, the single instance of the device controls upto 8 partitions.
When the minor device is created ddi_create_minor_node (that maps to a partition) with the DDI_NT_BLOCK_CHAN it creates a device with the names:
/dev/dsk/c2t2d190684ts0
/dev/dsk/c2t2d190684ts7
if the node is created with DDI_NT_BLOCK then it creates a device with the
names:
/dev/dsk/c2d2s0
/dev/dsk/c2d2s7
The device appears under the pci2f,4000/scsi device node, with scsi as part of the naming.
My questions are:
1) does a block device have to be known as a scsi device?
2) if does what additional properties must be supported. Are properties to be associated with the minor device numbers or instance of the device?

Well, I guess this may be thw wrong place to ask, as people in here tend to have already issues with their OVM installations and they probably don't know anything about OpenStack at all…
…I guess that's why you don't get any answer - wouldn't make sense for anyone to just reply, that they don't know OpenStack, would it?

Similar Messages

Raw device mapping

accidentally we lost the rawdevice mapping file /etc/sysconfig/rawdevices. since we do not have OS backup we could not restore this file.
without this file ASM could not mount diskgroups....
Is it possible to find the device mapping from anykind of OS or Oracle Log/Trace files?
Oracle alert log contains only /dev/raw/raw1....

Hi,
If the raw devices are still bound to the block device and you haven't rebooted since you lost you rawdevices config file then you could identify the major/minor numbers using /usr/bin/raw -qa
The example below shows that dev/raw/raw1 is bound to /dev/sdb1
[root@foo]# raw -qa
/dev/raw/raw1: bound to major 8, minor 17
[root@rmukvm214 dev]# ls -l sdb1
brw-rw---- 1 root disk 8, 17 Jun 17 16:14 sdb1
I'm not sure if this is the most elegant or safest way of piecing this information back together, as mentioned you might want to raise an SR with Oracle support.
Regards

Is it possible to block a number in iOS 6 but the same iphone number could be viewed as online on whatsapp application in the blocked device?

Is it possible to block a number in iOS 6 but the same iphone number could be viewed as online on whatsapp application in the blocked device?

Hi ChrisJ4203,
I see you didn't comment on editing the numbers in the keypad, I believe you have that problem too but you forgot to click "I have this question too".
By the way I've sent a couple feedback messages to Apple already and thanks for reminding me, I guess I'll have to be doing that more often.
Enjoy your day

Lucreate fails with: Root slice device ... for BE ... is not a block device

Hi,
I'm running lucreate on a Sol10u7 x86 system as I wanted to get it to u8 level. I installed:
SUNWlucfg
SUNWlur
SUNWluu
from u8 and then a patch: 121431-58
System is not zoned and it is on ZFS with following pools:
pool: rpool
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
c1t0d0s0 ONLINE 0 0 0
errors: No known data errors
pool: spool
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
spool ONLINE 0 0 0
c0t0d0 ONLINE 0 0 0
This is what happens:
Creating Alternative Boot Environment..
lucreate -n s10x_u8
Checking GRUB menu...
Analyzing system configuration.
No name for current boot environment.
INFORMATION: The current boot environment is not named - assigning name <s10x_u7wos_08>.
Current boot environment is named <s10x_u7wos_08>.
Creating initial configuration for primary boot environment <s10x_u7wos_08>.
The device </dev/dsk/c1t0d0s0> is not a root device for any boot environment; cannot get BE ID.
PBE configuration successful: PBE name <s10x_u7wos_08> PBE Boot Device </dev/dsk/c1t0d0s0>.
Comparing source boot environment <s10x_u7wos_08> file systems with the
file system(s) you specified for the new boot environment. Determining
which file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
Creating configuration for boot environment <s10x_u8>.
Source boot environment is <s10x_u7wos_08>.
Creating boot environment <s10x_u8>.
Cloning file systems from boot environment <s10x_u7wos_08> to create boot environment <s10x_u8>.
Creating snapshot for <rpool/ROOT/s10x_u7wos_08> on <rpool/ROOT/s10x_u7wos_08@s10x_u8>.
Creating clone for <rpool/ROOT/s10x_u7wos_08@s10x_u8> on <rpool/ROOT/s10x_u8>.
Setting canmount=noauto for </> in zone <global> on <rpool/ROOT/s10x_u8>.
Creating snapshot for <rpool/ROOT/s10x_u7wos_08/var> on <rpool/ROOT/s10x_u7wos_08/var@s10x_u8>.
Creating clone for <rpool/ROOT/s10x_u7wos_08/var@s10x_u8> on <rpool/ROOT/s10x_u8/var>.
Setting canmount=noauto for </var> in zone <global> on <rpool/ROOT/s10x_u8/var>.
ERROR: Root slice device </dev/dsk/c1t0d0s0> for BE <s10x_u8> is not a block device: .
ERROR: Cannot make file systems for boot environment <s10x_u8>.
Please help,
Cheers,
Tom

devfsadm fixed the issue,

SOLARIS 10 with iSCSI Problem "not a block device"

Hi Guys.
I almost reached it to build an iscsi connection with a Netgear readynas 2100.
But I have still one Point which makes me a Problem!!!
Everything works, except mounting the device....
It always Sais me: "not a block device"
At the bottom you can see an output of the whole configuration that I did.
Has anybody maybe a tip for me? Thanks in advance, Mischa
login as: root
Using keyboard-interactive authentication.
Password:
Last login: Fri Dec 18 01:18:30 2009 from pnm
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
Sourcing //.profile-EIS.....
root@sun001 # iscsiadm list discovery
Discovery:
Static: disabled
Send Targets: disabled
iSNS: disabled
root@sun001 # iscsiadm modify discovery -s enable
root@sun001 # iscsiadm modify discovery -t enable
root@sun001 # iscsiadm modify discovery -i enable
root@sun001 # devfsadm
root@sun001 # devfsadm -C
root@sun001 # ping 172.16.251.215
172.16.251.215 is alive
root@sun001 # iscsiadm list discovery
Discovery:
Static: enabled
Send Targets: enabled
iSNS: enabled
root@sun001 # iscsiadm add discovery-address 172.16.251.215
root@sun001 # iscsiadm list discovery-address
Discovery Address: 172.16.251.215:3260
root@sun001 # iscsiadm list discovery-address -v
Discovery Address: 172.16.251.215:3260
Target name: iqn.2009-12.Z-NAS-B0204:znaszim
Target address: 172.16.251.215:3260, 1
root@sun001 # format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t60014052E198270014ED001000000000d0 <DEFAULT cyl 65267 alt 2 hd 255 sec 63> znaszim1
/scsi_vhci/disk@g60014052e198270014ed001000000000
1. c3t0d0 <DEFAULT cyl 17747 alt 2 hd 255 sec 63>
/pci@7b,0/pci1022,7458@11/pci1000,3060@2/sd@0,0
2. c3t2d0 <DEFAULT cyl 17747 alt 2 hd 255 sec 63>
/pci@7b,0/pci1022,7458@11/pci1000,3060@2/sd@2,0
Specify disk (enter its number): ^C
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # dev
devattr devfree devfsadm devinfo devlinks devnm devreserv
root@sun001 # devfsadm -c iscsi
root@sun001 # iscsiadm list target -S
Target: iqn.2009-12.Z-NAS-B0204:znaszim
Alias: LIO Target
TPGT: 1
ISID: 4000002a0000
Connections: 1
LUN: 0
Vendor: LIO-ORG
Product: FILEIO
OS Device Name: /dev/rdsk/c1t60014052E198270014ED001000000000d0s2
root@sun001 # mkdir /export/iscsi
root@sun001 # mount /dev/rdsk/c1t60014052E198270014ED001000000000d0s2 /export/iscsi/
mount: /dev/rdsk/c1t60014052E198270014ED001000000000d0s2 not a block device
root@sun001 #
-----------------------------------------------------------------

Ok. Sorry i have to explaine it in an other way.
The Storage Device is a Netgear Ready NAS 2100.
Netgear Ready NAS with a Linux os.
The OS Supports different Protocols like: CIFS / FTP / HTTP/ iSCSI etc...
Now im trying to use an other protocoll (cifs) to store the data on the Netgear NAS.
i found smbclient and was able to open a connection to the NAS.
root@sun001 # /usr/sfw/bin/smbclient //172.20.0.51/video_net -U usrvideo
Password:
Domain=[Z-NAS-A0111] OS=[Unix] Server=[Samba 3.4.5]
smb: \> ls
. D 0 Tue Feb 23 11:12:04 2010
.. D 0 Thu Feb 18 10:38:52 2010
172.22.1.58.lnk A 747 Fri Feb 19 19:18:37 2010
172.22.1.55.lnk A 747 Fri Feb 19 18:41:07 2010
65535 blocks of size 33553920. 65535 blocks available
smb: \>
Is there a way to mount the smb connection when the server starts up?
I have to find a way to attach the NAS like a local folder...
And that is why i choose iSCSI before..
Regards
mischa
Edited by: mischu on Feb 26, 2010 2:34 AM

File is not a BLOCK device

Hi,
Trying to configure ASM on this device and getting the error:
eating /dev/oracleasm mount point: /dev/oracleasm
Loading module "oracleasm": oracleasm
Configuring "oracleasm" to use device physical block size
Mounting ASMlib driver filesystem: /dev/oracleasm
Reloading disk partitions: done
Cleaning any stale ASM disks...
Scanning system for ASM disks...
File "/oracle/asm/disks/nfsdisk1" is not a block device
File "/oracle/asm/disks/nfsdisk1" is not a block device
File "/oracle/asm/disks/nfsdisk1" is not a block device
Cleaning any stale ASM disks...
Unmounting ASMlib driver filesystem: /dev/oracleasm
Unloading module "oracleasm": oracleasm
Loading module "oracleasm": oracleasm
Configuring "oracleasm" to use device physical block size
Mounting ASMlib driver filesystem: /dev/oracleasm
Reloading disk partitions: done
Cleaning any stale ASM disks...
Scanning system for ASM disks...
Reloading disk partitions: done
Cleaning any stale ASM disks...
Scanning system for ASM disks...
File "/oracle/asm/disks/nfsdisk1" is not a block device
What has been done:
dd if=/dev/zero of=/oracle/asm/disks/nfsdisk1 bs=8192 count=100000
100000+0 records in
100000+0 records out
819200000 bytes (819 MB) copied, 90.3162 s, 9.1 MB/s
also:
/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface [oracle]:
Default group to own the driver interface [dba]:
Start Oracle ASM library driver on boot (y/n) [y]:
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
not sure what else to do..
thanks

Hi,
To create Oracle ASM disks, there are some steps to do:
- Have raw Disks, and you don't have then you can create a pseudo disks with the command dd us yours.
- Install ASMLib
- Use the /etc/init.d/oracleasm to configure, create ASM disks
The command dd creates a pseudo-block disk, and this a solution: Create virtual RAW disks for Oracle ASM on Linux with single Hard Drive
# dd if=/dev/zero of=/asm/disk4 bs=1M count=2000
# losetup /dev/loop4 /asm/disk4
# /etc/init.d/oracleasm createdisk ASM4 /dev/loop4
After the creation, you should scan your ASM disks: Wadhah DAOUEHI - Creation of ASM disks on Oracle Linux using ASMLib
# /etc/init.d/oracleasm scandisks
# /etc/init.d/oracleasm listdisks
Best regards

Can't have ASM mark a NFS file as an ASM disk : -is not a block device

Hello,
I’m trying to experiment with ASM for learning purpose. Because I don’t have access to a SAN, I am trying to use NFS files but I can’t manage to have ASM mark those files as ASM disks.
[root@localhost /]# /etc/init.d/oracleasm createdisk ASM_DISK_1 /mnt/asm_dsks/dg1/disk1
Marking disk "ASM_DISK_1" as an ASM disk: [FAILED]
The oracleasm log says: File "/mnt/asm_dsks/dg1/disk1" is not a block device
OK, more context now:
I am trying to install ASM on a RHEL5 virtual machine (on vmware).
[root@localhost /]# uname -rm
2.6.18-8.el5 x86_64
I followed this document:
http://www.oracle.com/technology/pub/articles/smiley-11gr1-install.html until I got stuck at the following command:
/etc/init.d/oracleasm createdisk ...
Now, the NFS filesystem comes from a Solaris 10 system (the only one that's available) running on a physical sun box (this one is not a virtual system).
I have tried many combinations. I tried creating the files on the linux VM, using dd. As root, as oracle. I tried creating them on the Solaris side, using mkfile... no matter what I try, I always get the same issue.
I tried to follow this document: Creating Files on a NAS Device for Use with ASM (http://download.oracle.com/docs/html/B10811_05/app_nas.htm#BCFHCIEC)
But nothing seems to work.
Any idea, recommendations?
Thanks,
Laurent.

Hi buddy,
I guess the metalink note 731775.1 should help You.
In fact the procedure is:
- Create the disk devices on your NFS directory (using dd)
- Adjuste the permissions over those files (in this case, oracle:dba)
- Adjust the ASM_DISKSTRING at the ASM instance and setting the NFS directory in the discovery path
- Verify if they are available at v$asm_disk view
- Create the diskgroup using the the NFS disks that You have created.
Hope it helps,
Cerreia

User Mode Block Device Driver

Hi,
I want to write a block device driver in user mode so that the read and write calls from the FileSystem comes to user mode component than a regular kernel mode driver.
why i want to do this ... because I want to pass on the data coming to another apps and the data is near real time and large. So, I can't keep the block driver in kernel mode and do transfer of data from kernel mode to user mode.
Can this be done ... ? I have been looking at various things but nothing comes close. Any hints will be helpful.
Thanks
Tarrot .

Well. The 2 user apps cannot talk directly as User APPs2 only understands block I/O requests as input so it has to have a FS over it which is ext3. User APPs1 is an application that runs over FS and writes to it like windows explorer.
The Problem is I am not able to find a way to write a user mode block driver. Why I want this to be user mode so that I can interface to Virtual disk below which is a user mode application, i.e. User Apps2.
I can write a kernel mode block driver there but it would not be efficient as I will have to push it from kernel mode to user mode for userapps2.
I hope it explains....

[SOLVED] /dev/root is not a valid block device

After trying to boot my system after a few days of it remaining off, it fails to boot with:
Booting the kernel.
ERROR: resume: hibernation device '/dev/sda9' not found
mount: /dev/root is not a valid block device
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off.
[rootfs /]#
The sda9 error has been around for quite some time, even back when it was working and I've been ignoring it all these days.
Last edited by SgrA (2013-03-28 18:00:35)

I did try that. Now after a few suggestions on #archlinux, I'm using LABEL's instead of device names, and SYSLINUX. The scene isn't much different, now it complains that it can't find "LABEL=Arch" instead. Here's the current fstab:
# <file system> <dir> <type> <options> <dump> <pass>
LABEL=Boot /boot ext2 defaults 0 1
UUID=c9e24897-af78-4768-bf67-2302ebf17a2b /mnt/Algenib ext4 defaults 0 1
LABEL=Arch / ext4 defaults 0 1
UUID=2cc33548-62ef-4c22-a2c8-13bb5a979273 /mnt/Acrux ext4 defaults 0 1
UUID=cd53f792-f142-45b2-aa0c-ab314950b53b /mnt/Mimosa ext4 defaults 0 1
UUID=122606f2-7ef7-4746-a688-806caaacc86f /mnt/Gacrux ext4 defaults,noauto 0 1
UUID=5b4c6ccb-b90c-488b-aa5d-135a2e98eaf0 swap swap defaults 0 0
and here's syslinux.cfg:
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: [url]https://wiki.archlinux.org/index.php/Syslinux[/url]
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to [url]http://syslinux.zytor.com/wiki/index.php/Doc/menu[/url]
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=LABEL=Arch ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=LABEL=Arch ro
INITRD ../initramfs-linux-fallback.img
LABEL algenib
MENU LABEL Algenib
LINUX ../vml-alg
APPEND root=UUID=c9e24897-af78-4768-bf67-2302ebf17a2b
INITRD ../ini-alg
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com
This is what happens:
http://i.imgur.com/cVh1l1l.jpg
Last edited by SgrA (2013-03-28 13:20:22)

How to set permissions on devicemapper block device

I'm setting up a new RAC on RHEL5.1 using device mapper for multipath functionality.
How should I set the permissions for the block devices I'm going to use for ocr, voting and asm?
/dev/mapper/ocr1
/dev/mapper/voting1
etc.
Regards
Jon-Arne Storelv

Markus,
You are right about udev changing drastically between RHEL 4 and RHEL 5. The paper I referred to does include some guidelines for setting permissions for RHEL 5 as well. Here are some relevant extracts from the same pdf document:-
# From udev.permissions section
This file was obsoleted in later versions of the 2.6 kernels such as SLES10, RHEL5 and
Oracle Enterprise Linux 5 (OEL5), that functionality was merged into the rules files, which is explained later in this paper
...and later you will find this example in the document
For RHEL5, OEL5, SLES10
• Create a file /etc/udev/rules.d/99-raw.rules with the following content
with the following content
KERNEL=="raw[1-2]*", GROUP="oinstall", MODE="640"
KERNEL=="raw[3-5]*", OWNER="oracle", GROUP="oinstall", MODE="660"
/etc/udev/rules.d/50-udev.rules on Centos 5 gives plenty of examples of settings for all different types of devices. We really need to specify OWNER, GROUP and MODE for devices that RAC will use in a rules file.
Thanks,
Satish

Oracle VM Migrating virtual disk images to physical disks (block devices)

Hi,
For performance reasons, I'd like to migrate my .img file based virtual disks into physical partitions for VM's.
What is the safest possible way to migrate all partitions (including / partition) from a virtual disk to a block device?
Thanks,
Onur

hobeygo wrote:
What is the safest possible way to migrate all partitions (including / partition) from a virtual disk to a block device?Create block devices the same size as your .img files and then use dd to copy the contents of the .img file to the block device. Your VMs need to be offline while you do this. Once you've done this, you can use Oracle VM Manager to remove the original .img file and replace it with the physical block device copy. This is low-risk, as the .img file will still be there if the new block device doesn't work.
Keep in mind that you will need a unique block device for every .img file you have.

Mount: not a block device

i have created a solaris lun and trying to view the same from my solaris console. i want to perform i/o operations on the lun; how do i mount it? 'coz mount command gives "not a block device" error.

It depends on the specific driver, but you usually want to mount the 'dsk' device and not the 'rdsk' device.
Darren

Kernel 3.8.8-1 can't find any block device

After last kernel upgrade boot process stoped at "wait for root device".
There is nothing about initializing disk drives in dmesg and no block devices listed in /dev. There is no /dev/disk directory too.
I do have 3 disk drives. The devices are connected and present in bios. I am pretty sure they are fine.
Any idea what is going on?

I didn't notice any errors on the upgrade. Fallback image is dead too. Where is my usb stick...

I wrote a filter driver over block device.

HI,
I wrote a virutal volume driver over block device , simlar with LVM,
I call it "vraid" ,I can create PV,VG,LV,it's working well.
However I cannot acess the sector over 2G , I can use the system
command "newfs -s XXXX /dev/vlun/rdsk/vlun0" to create a 2G filesystem.
If I use newfs /dev/vlun/rdsk/vlun0 to create the file system in the whole LV size,I found
If LV>2G ,the sector beyond 2G will not be located correctly. output as below.
seek\:XXXXXX Invalid argument.
So I use the system c ommand "truss" to trace the command mkfs (newfs invoke mkfs finally) ,
I found the llseek() is the matter,
When llseek() is invoked, I trace d all system callings,I found if I use llseek() to
locate some sectors, however there is no any callings ocurred in my drvier besides the
calling open() and close()/
I wonder to know why I always failed to acess the sector over 2G .
thanks and happies.
I'm sorry my poor English/
I'm in China. and I'm a Chinese girl.
Ms. Anda

My makefile is the following.:
# CC = /opt/SUNWspro/bin/cc
CC = /usr/local/bin/gcc
LD = /usr/ucb/bin/ld
# 'uname -p' command
INST = i386
INCL = -I . -I $(TOPDIR)/include
#gcc
CFLAGS = -O $(INCL) -D_KERNEL -DOS_SOLARIS -Wall
TOPDIR = ../..
BUILD = vraid
OBJS = _vraid.o \
raid0.o \
raid1.o \
multicopy.o \
snapshot.o \
queue.o \
hash.o \
rand.o
$(BUILD) vraid_driver_setup.bin:$(OBJS)
$(LD) -r -o $(BUILD) $(OBJS)
sh -c ./generate_bin_install.sh
hash.o:hash.c
$(CC) $(CFLAGS) -o hash.o -c hash.c
_vraid.o:vraid.c
$(CC) $(CFLAGS) -o _vraid.o -c vraid.c
raid0.o:raid0.c
$(CC) $(CFLAGS) -o raid0.o -c raid0.c
raid1.o:raid1.c
multicopy.o:multicopy.c
$(CC) $(CFLAGS) -o multicopy.o -c multicopy.c
queue.o:queue.c
$(CC) $(CFLAGS) -o queue.o -c queue.c
snapshot.o:snapshot.c
$(CC) $(CFLAGS) -o snapshot.o -c snapshot.c
rand.o:rand.c
$(CC) $(CFLAGS) -o rand.o -c rand.c
clean:
rm -rf $(OBJS) $(BUILD) vraid_driver_setup.bin

RAC on EMC block devices

I have finished installing a 11g RAC on RHELv5 using EMC block devices for storage.
During installation i had partitioned the disks and changed ownership to oracle:dba
However everytime i reboot the server, the block devices ownership is reverted back to root and hence CRS doesnt fails to come up. So i end up doing a manual change in ownership and permission to bring up the CRS, ASM and finally the database.
Is there any way, i can automate this?
Thanks in Advance.

You can setup this in udev permissnion file. In OEL5 it looks like:
[root@rick oracle]# tail -8 /etc/udev/rules.d/50-udev.rules
KERNEL=="sdb1", OWNER="root", GROUP="oinstall", MODE="640"
KERNEL=="sdc1", OWNER="oracle", GROUP="oinstall", MODE="640"
KERNEL=="sdd1", OWNER="oracle", GROUP="dba", MODE="640"
KERNEL=="sde1", OWNER="oracle", GROUP="dba", MODE="640"
KERNEL=="sdf1", OWNER="oracle", GROUP="dba", MODE="640"
KERNEL=="sdg1", OWNER="oracle", GROUP="dba", MODE="640"

Block Device Mapping

Similar Messages

Maybe you are looking for