Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 06-22-2017, 03:26 AM   #1
LQ Newbie
Registered: Jun 2017
Posts: 4

Rep: Reputation: Disabled
NetApp SAN Issuu

the ownerships and permissions are wiped out and devices permissions revert back to original root:disk. Due to this oracle software does not works properly as it is installed using oracle install user/group
Old 06-22-2017, 04:23 AM   #2
LQ Guru
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524

Rep: Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015
Hi verrinder.

Welcome to LQ!

Start at the beginning. We can't read your mind. Please give a good explanation of the problem.
Old 06-22-2017, 06:12 AM   #3
Registered: Jan 2017
Location: Fremont, CA, USA
Distribution: Trying any&ALL on old/minimal
Posts: 997

Rep: Reputation: 382Reputation: 382Reputation: 382Reputation: 382
Linux, by default, places detected disk volumes under /dev/ with root:disk as user/group (for example, /dev/sdq) and not read/writeable for anyone else than root user/group. So Oracle cannot handle this as it typically does not run under root id. Also, if ASM scans /dev/ it will have to scan a lot of devices because /dev/ is home to not just all disks, but also all other block (and character) devices.
So we need to present ASM volumes under a path that matches the ASM diskstring and has different userid/group and permissions. One way of doing this is using the “mknod” command to create references (inodes) to the disks under /dev. So for example /dev/sdq and /dev/oracleasm/disks/myvol both point to a Linux device with major ID 8 and minor id 80. They are essentially different names for the very same thing and can have different permissions (so /dev/sdq can have root:root and myvol can have oracle:asm as ownership and still being the same device). The problem is that a) it’s a very manual intensive process, b) it’s error prone and c) not guaranteed to be consistent across reboots.


Oracle therefore created a tool called ASMLib that consisted of a custom kernel module and a set of command line tools. The kernel module (driven by the CLI) would scan all devices in /dev/* after boot and if it found the right signatures it would clone those (by creating additional device inodes using mknod) typically using diskstring /dev/oracleasm/disks.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
company moved from EMC SAN to Netapp sam_nyc Linux - Newbie 2 09-05-2012 02:25 AM
Emluex SAN not visible in RHEL 5.6. SAN array is HP XP12000 austinbravo Linux - Newbie 0 07-26-2011 09:38 PM
Can no longer connect to san device when san switch changed rew25 Linux - Hardware 2 09-07-2010 09:28 AM
Unable to connect to NetApp SAN using RHEL 4 and software iSCSI Initiator saldon Linux - Server 1 07-13-2008 05:32 AM
Unable to connect to NetApp SAN using RHEL 4 and software iSCSI Initiator saldon Linux - Desktop 3 07-11-2008 04:28 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 04:49 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration