8 Replies Latest reply on Feb 18, 2013 1:47 PM by Levi Pereira

    ASM Device Blocks from DISK GROUP

      Hi Experts,

      Need your expertise in finding the issues.

      Currently we are in Linux RHEL 6, oracle

      We dont have oracleasm binaries but using udev.

      We have 12 ASM DISK groups with names ASM_DISK_01... ASM_DISK_12

      All I am interested is how can I see where the block devices are mapped .

      i.e ASM_DISK_01 is mapped to /dev/sd1 on the host... like that which file i need to check.

      I tried /dev/mapper/*permissiom* file ...but no luck .

      Please help
        • 1. Re: ASM Device Blocks from DISK GROUP
          Victor Armbrust
          Have you try "/etc/init.d/oracleasm querydisk -d ASM_DISK_01" ?
          try on all your disk labels.

          • 2. Re: ASM Device Blocks from DISK GROUP
            As i said we are not using any oracleasm binary.

            We dont have that binary file in that location.
            • 3. Re: ASM Device Blocks from DISK GROUP
              Victor Armbrust
              Do you have a ASM instance up? you can check the labels/path/name using v$asm_diskgroup.
              • 4. Re: ASM Device Blocks from DISK GROUP
                Yes its up and running.

                But I want to get the info from UNIX level.

                If I login to ASM i can get info. but beyond that I would like to see the info
                • 5. Re: ASM Device Blocks from DISK GROUP
                  Oracle is not supporting Red Hat Linux 6.x with the asmLib files. It is supporting the Oracle version of Linux, however it is no longer supplying the asmlib disk management utilities as it did in the Red Hat Linux 5.x release. You really don't need the asmlib because Red Hat Linux is provides the disk/device management with udev.

                  I have just successfully implemented Red Hat Linux 6.3 using Oracle Grid Infrastructure ASM and Oracle Real Application Cluster (RAC) release and it working like a charm. At first I thought that I had to do a lot of things differently and thinking that it was time as we know it has changed (mayan calendar end) however we are just in a different time and Oracle 11gR2 ( Grid Infrastructure and Red Hat Linux 6.3 are a great compliment.

                  Oracle continues to improve on its Grid Infrastructure ASM and Real Application Cluster ASM as Red Hat Linux continues to provide improved functionality and enterprise management.

                  I'm preparing to post my most recent build.

                  Edited by: yakub21 on Feb 13, 2013 6:14 PM
                  • 6. Re: ASM Device Blocks from DISK GROUP
                    Thanks Yakub For the info.

                    Even I have installed succesfully and we are also using the udev .

                    All I am looking is the ASM disks mapping to Physical disks.

                    like for ex.

                    /dev/oracleasm/disks/ASMDSK-1 will be physcially mapped to /dev/sd2

                    With out root how can a DBA find out ... this is what am looking for

                    Any help is appreciated.
                    • 7. Re: ASM Device Blocks from DISK GROUP
                      What makes you think that there was any disk to device mapping? ASM uses metadata stored on the disk. e.g.:

                      od -c /dev/sdb1 |head -10
                      0000000 001 202 001 001 \0 \0 \0 \0 \0 \0 \0 200 247 275 024 +
                      0000020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
                      0000040 O R C L D I S K A S M 1 \0 \0 \0 \0
                      0000060 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
                      • 8. Re: ASM Device Blocks from DISK GROUP
                        Levi Pereira

                        You can use KFOD utility.
                        I recommend you run command below as grid user and $GRID_HOME.

                        You will get a nice report with command below:
                        $ kfod asm_diskstring=/dev/rh* disks=all  dscvgroup=TRUE status=true
                        P.S : If the permission/owner was changed and you is trying to find what disks is a member of ASM then run the command above as root user.


                        Keep in mind that the Grid Infrastructure software does not need to be installed to use kfod, since kfod is located as well on the staging area where you uncompressed the Grid Infrastructure software, as the following example:

                        Where: "/stage" is the directory where I uncompressed the source software for the Grid Infrastructure software.

                        Levi Pereira

                        Edited by: Levi Pereira on Feb 18, 2013 10:46 AM