Re: Linux Native Multipath, ASM and Instance Failures

  • From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
  • To: Ls Cheng <exriscer@xxxxxxxxx>
  • Date: Sat, 28 Jul 2012 11:18:15 -0300

So,
  I've narrowed this down a little. It turns out that the hosts that are
crashing when a path goes down are, in fact, using ASMLib. So at this point
I need a window in which to change the scanorder to /dev/dm /dev/mapper and
retest. Don't know if I'll get to do that, though.


  Cheng, we use /dev/mapper. so in your case you should have a
/dev/mapper/3PAR_kenan_data_dsk01 and when you use fdisk (or kpartx?) to
create a single primary partition spanning the entire disk, and after
running multipath -F and multipath -ll, you will get a /dev/mapper/
3PAR_kenan_data_dsk01p1, which is the actual disk you will use on ASM. If
you are using ASMLib, then you'll add the disk and be done with it, if you
are not using ASMLib, the diskstring should look like '/dev/mapper/*p1' to
ensure you're always hitting the correct partition.

  Also, there's a very good whitepaper out there about 3PAR, ASM,
Multipath. A quick recommendation, set NO_PATH_RETRY to 12 and
POLLING_INTERVAL to 5 or 10, depending on your needs.

  I couldn't find a link to it, but the HP part number is: QL226-96598

Cheers
Alan.-


On Sat, Jul 28, 2012 at 6:18 AM, Ls Cheng <exriscer@xxxxxxxxx> wrote:

> it looks as following:
>
>         multipath {
>                           wwid    350002ac0001d2361
>                           alias   3PAR_kenan_data_dsk01
>         }
>
> Thanks
>
>
>


--
//www.freelists.org/webpage/oracle-l


Other related posts: