Re: Linux Native Multipath, ASM and Instance Failures

  • From: Ls Cheng <exriscer@xxxxxxxxx>
  • To: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
  • Date: Sat, 28 Jul 2012 19:17:56 +0200

I have the doc you are saying, it is the one I am using
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03290635/c03290635.pdf


in page 32 you can see what you need to use for path failover policy and
pther storage features in multipath.conf, it is multibus because 3PAR says
so, other storage arrays have other configurations;

# HP EVA
device {
        vendor                  "HP|COMPAQ"
        product                 "HSV1[01]1
\(C\)COMPAQ|HSV[2][01]0|HSV300|HSV4[05]0"
        path_grouping_policy    group_by_prio
        getuid_callout          "/lib/udev/scsi_id -g -u /dev/%n"
        path_checker            tur
        path_selector           "round-robin 0"
        prio                    alua
        rr_weight               uniform
        failback                immediate
        hardware_handler        "0"
        no_path_retry           18
        rr_min_io               100
}

# Device attributed for EMC CLARiiON and VNX series ALUA
device {
vendor "DGC"
product "*"
prio_callout "/sbin/mpath_prio_alua /dev/%n"
path_grouping_policy group_by_prio
features "1 queue_if_no_path"
failback immediate
hardware_handler "1 alua"
}
}


I would not change anything there because this configuration is provided by
the storage maker

If you read 3PAR doc, page 70, you can see what I have said in other mail:

*NOTE: Do not use the fdisk command with /dev/mapper/XXX devices to create
partitions*

But that is not true, other makers says we must run fdisk to
/dev/mapper/XXX devices, MOS notes as well


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

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 07-2012