Scribd
Upload
987 views3 pages

Multipath - Conf HITACHI

This document contains an example configuration file for device mapper multipath. It lists default configuration values that are located in specific files and provides commented examples of configuration options and how to blacklist devices. Specific HITACHI storage devices are configured with custom path grouping policies and callouts.

Uploaded by

Breno Rodrigues
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
987 views3 pages

Multipath - Conf HITACHI

This document contains an example configuration file for device mapper multipath. It lists default configuration values that are located in specific files and provides commented examples of configuration options and how to blacklist devices. Specific HITACHI storage devices are configured with custom path grouping policies and callouts.

Uploaded by

Breno Rodrigues
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

#

#
#
#
#
#

This is a basic configuration file with some examples, for device mapper
multipath.
For a complete list of the default configuration values, see
/usr/share/doc/device-mapper-multipath-0.4.7/multipath.conf.defaults
For a list of configuration options with descriptions, see
/usr/share/doc/device-mapper-multipath-0.4.7/multipath.conf.annotated

##VERIFICAR CAMINHO CALLOUT


### SE ESTIVER ESTE
### prio_callout

"/sbin/pp_hds_modular %d"

###SUBSTITUIR POR ESTE


###prio_callout

"/sbin/mpath_prio_hds_modular %d"

# Blacklist all devices by default. Remove this to enable multipathing


# on the default devices.
blacklist {
devnode "*"
}
## By default, devices with vendor = "IBM" and product = "S/390.*" are
## blacklisted. To enable mulitpathing on these devies, uncomment the
## following lines.
#blacklist_exceptions {
#
device {
#
vendor "IBM"
#
product "S/390.*"
#
}
#}
## Use user friendly names, instead of using WWIDs as names.
defaults {
user_friendly_names yes
}
##
## Here is an example of how to configure some standard options.
##
#
#defaults {
#
udev_dir
/dev
#
polling_interval
10
#
selector
"round-robin 0"
#
path_grouping_policy
multibus
#
getuid_callout
"/sbin/scsi_id -g -u -s /block/%n"
#
prio_callout
/bin/true
#
path_checker
readsector0
#
rr_min_io
100
#
max_fds
8192
#
rr_weight
priorities
#
failback
immediate
#
no_path_retry
fail
#
user_friendly_names
yes
#}
##
## The wwid line in the following blacklist section is shown as an example
## of how to blacklist devices by wwid. The 2 devnode lines are the

## compiled in default blacklist. If you want to blacklist entire types


## of devices, such as all scsi devices, you should use a devnode line.
## However, if you want to blacklist specific devices, you should use
## a wwid line. Since there is no guarantee that a specific device will
## not change names on reboot (from /dev/sda to /dev/sdb for example)
## devnode lines are not recommended for blacklisting specific devices.
##
#blacklist {
#
wwid 26353900f02796769
#
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
#
devnode "^hd[a-z]"
#}
#multipaths {
#
multipath {
#
wwid
3600508b4000156d700012000000b0000
#
alias
yellow
#
path_grouping_policy
multibus
#
path_checker
readsector0
#
path_selector
"round-robin 0"
#
failback
manual
#
rr_weight
priorities
#
no_path_retry
5
#
}
#
multipath {
#
wwid
1DEC_____321816758474
#
alias
red
#
}
#}
#devices {
#
device {
#
vendor
"COMPAQ "
#
product
"HSV110 (C)COMPAQ"
#
path_grouping_policy
multibus
#
getuid_callout
"/sbin/scsi_id -g -u -s /block/%n"
#
path_checker
readsector0
#
path_selector
"round-robin 0"
#
hardware_handler
"0"
#
failback
15
#
rr_weight
priorities
#
no_path_retry
queue
#
}
#
device {
#
vendor
"COMPAQ "
#
product
"MSA1000
"
#
path_grouping_policy
multibus
#
}
#}
defaults {
polling_interval 120
udev_dir /dev
default_path_grouping_policy failover
rr_weight priorities
failback immediate
}
blacklist {
devnode
devnode
devnode
devnode

cciss
fd
hd
md

devnode
devnode
devnode
devnode
devnode
devnode
devnode
devnode

sr
scd
st
ram
raw
loop
sda # internal disk
sdb # internal disk

}
multipaths {
multipath {
wwid "360060e801005b030052fb7b300000027"
alias "DGORA01"
}
}
devices {
device {
vendor
product
path_grouping_policy
prio_callout
path_checker
getuid_callout

"HITACHI"
"DF600F"
group_by_prio
"/sbin/mpath_prio_hds_modular %d"
readsector0
"/sbin/scsi_id -g -u -s /block/%n"

}
device {
vendor
product
path_grouping_policy
prio_callout
path_checker
getuid_callout

"HITACHI"
"DF600F-CM"
group_by_prio
"/sbin/mpath_prio_hds_modular %d"
readsector0
"/sbin/scsi_id -g -u -s /block/%n"

}
device {
vendor
product
path_grouping_policy
path_checker
getuid_callout

"HITACHI"
"OPEN-V"
multibus
readsector0
"/sbin/scsi_id -g -u -s /block/%n"

}
device {
vendor
product
path_grouping_policy
path_checker
getuid_callout
}
}

"HITACHI"
"OPEN-V-CM"
multibus
readsector0
"/sbin/scsi_id -g -u -s /block/%n"

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy