1 |
Am 12.09.18 um 15:07 schrieb J. Roeleveld: |
2 |
|
3 |
> Bit sooner: |
4 |
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/ |
5 |
> dm_multipath/mpio_overview |
6 |
> |
7 |
> https://www.thegeekdiary.com/beginners-guide-to-device-mapper-dm-multipathing/ |
8 |
> |
9 |
> |
10 |
> I use multipath from a SAS-controller to a dual-backplane and SAS-disks. |
11 |
> From the controller, I have 2 paths to each disk, which means I have twice the |
12 |
> amount of "sd?" entries. |
13 |
> |
14 |
> == |
15 |
> # multipath -l |
16 |
> 35000cca25d8ec910 dm-4 HGST,HUS726040ALS210 |
17 |
> size=3.6T features='1 retain_attached_hw_handler' hwhandler='0' wp=rw |
18 |
> |-+- policy='service-time 0' prio=0 status=active |
19 |
> | `- 0:0:7:0 sdh 8:112 active undef running |
20 |
> `-+- policy='service-time 0' prio=0 status=enabled |
21 |
> `- 0:0:20:0 sdt 65:48 active undef running |
22 |
> == |
23 |
> (This is only the first device) |
24 |
> |
25 |
> It shows that device "35000cca25d8ec910" is mapped to "sdh" and "sdt". |
26 |
> To use the disk correctly, I need to access "/dev/mapper/35000cca25d8ec910", |
27 |
> which is: |
28 |
> # ls -lsa /dev/mapper/35000cca25d8ec910 |
29 |
> 0 lrwxrwxrwx 1 root root 7 Sep 4 11:43 /dev/mapper/35000cca25d8ec910 -> ../ |
30 |
> dm-4 |
31 |
> |
32 |
> I have "multipathd" in the "boot" runlevel. |
33 |
> |
34 |
> Version info: |
35 |
> # eix -I multipath |
36 |
> [I] sys-fs/multipath-tools |
37 |
> Available versions: 0.5.0-r1 0.6.4-r1{tbz2} ~0.7.6^t ~0.7.7^t {rbd |
38 |
> systemd KERNEL="linux"} |
39 |
> Installed versions: 0.6.4-r1{tbz2}(10:51:01 AM 01/23/2018)(-rbd - |
40 |
> systemd) |
41 |
> Homepage: http://christophe.varoqui.free.fr/ |
42 |
> Description: Device mapper target autoconfig |
43 |
> |
44 |
> # uname -a |
45 |
> Linux san1 4.9.76-gentoo-r1-generic #1 SMP Tue Jan 23 12:05:11 CET 2018 x86_64 |
46 |
> Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz GenuineIntel GNU/Linux |
47 |
> |
48 |
> As for the terms, a LUN is a Logical disk provided by a SAN to a different |
49 |
> system. I have multipath inside my SAN and have a single path to iSCSI |
50 |
> clients. (Single switch with bonded NICs) |
51 |
|
52 |
thanks for the links etc |
53 |
|
54 |
To me it seems that the former administrator somehow tried to set that |
55 |
up but failed. |
56 |
|
57 |
This corresponds to something he wrote when leaving the company. |
58 |
|
59 |
There is no multipathd-daemon enabled or running. |
60 |
|
61 |
# multipath |
62 |
Sep 14 08:31:10 | MSA2040_SAMBA_storage: ignoring map |
63 |
Sep 14 08:31:10 | MSA2040_SAMBA_storage: ignoring map |
64 |
|
65 |
# multipath -l |
66 |
# |
67 |
|
68 |
# ls /dev/mapper/ |
69 |
control |
70 |
|
71 |
|
72 |
so nothing gets mapped here ;-) |
73 |
|
74 |
- |
75 |
|
76 |
# /etc/multipath.conf |
77 |
|
78 |
defaults { |
79 |
# udev_dir /dev |
80 |
polling_interval 15 |
81 |
# selector "round-robin 0" |
82 |
path_grouping_policy group_by_prio |
83 |
failback 5 |
84 |
path_checker tur |
85 |
# prio_callout "/sbin/mpath_prio_tpc /dev/%n" |
86 |
rr_min_io 100 |
87 |
rr_weight uniform |
88 |
no_path_retry queue |
89 |
user_friendly_names yes |
90 |
} |
91 |
blacklist { |
92 |
devnode cciss |
93 |
devnode fd |
94 |
devnode hd |
95 |
devnode md |
96 |
devnode sr |
97 |
devnode scd |
98 |
devnode st |
99 |
devnode ram |
100 |
devnode raw |
101 |
devnode loop |
102 |
devnode sda |
103 |
devnode sdb |
104 |
} |
105 |
|
106 |
multipaths { |
107 |
multipath { |
108 |
wwid 3600c0ff0001e91b2c1bae25601000000 |
109 |
## To find your wwid, please use /usr/bin/sg_vpd --page=di /dev/DEVICE. |
110 |
## The address will be a 0x6. Remove the 0x and replace it with 3. |
111 |
alias MSA2040_SAMBA_storage |
112 |
} |
113 |
} |
114 |
|
115 |
|
116 |
--- I will check docs etc asap |
117 |
That is a productive server a few 100 kms away from me, so I have to be |
118 |
careful. |
119 |
|
120 |
Users can work, so no hurry here, just interest. |