From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] multipath.conf : learning how to use
Date: Wed, 14 Aug 2019 10:14:31 +0200 [thread overview]
Message-ID: <38401489-dffa-b3e8-422f-3d3585ae74ad@xunil.at> (raw)
In-Reply-To: <3271924.fr91aXinDs@andromeda>
Am 14.08.19 um 08:36 schrieb J. Roeleveld:
> Stefan,
>
>
> On maandag 29 juli 2019 21:28:50 CEST Stefan G. Weichinger wrote:
>> At a customer I have to check through an older gentoo server.
>>
>> The former admin is not available anymore and among other things I have
>> to check how the SAN storage is attached.
>
> If you ever encounter that admin, make sure you hide the body :)
I only learn day by day what a mess all that is ...
>> I see two devices sdc and sdd that should come from the SAN.
>
> Interesting, are these supposed to be the same?
No, I don't think so. But maybe you'r right. No sdd in fstab or in the
mounts at all and ...
> what do you get back from:
>
> # /usr/bin/sg_vpd --page=di /dev/sdc
> # /usr/bin/sg_vpd --page=di /dev/sdd
> (As suggested in the multipathd.conf file you listed above)
these 2 look similar to me:
samba ~ # /usr/bin/sg_vpd --page=di /dev/sdc
Device Identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x600c0ff0001e91b2c1bae25601000000
designator type: vendor specific [0x0], code set: Binary
vendor specific:
00 11 32 36 37 32 31 36 00 00 c0 ff 1e 91 b2 00 00 .267216.........
10 c0 a8 64 12 00 c0 ff 1e 8d 38 00 00 c0 a8 64 11 ..d......8....d.
Target port:
designator type: Relative target port, code set: Binary
Relative target port: 0x3
designator type: Target port group, code set: Binary
Target port group: 0x0
designator type: NAA, code set: Binary
transport: Fibre Channel Protocol for SCSI (FCP-4)
0x227000c0ff267216
Target device that contains addressed lu:
designator type: NAA, code set: Binary
transport: Fibre Channel Protocol for SCSI (FCP-4)
0x208000c0ff267216
samba ~ # /usr/bin/sg_vpd --page=di /dev/sdd
Device Identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x600c0ff0001e91b2c1bae25601000000
designator type: vendor specific [0x0], code set: Binary
vendor specific:
00 11 32 36 37 32 31 36 00 00 c0 ff 1e 8d 38 00 00 .267216......8..
10 c0 a8 64 11 00 c0 ff 1e 91 b2 00 00 c0 a8 64 12 ..d...........d.
Target port:
designator type: Relative target port, code set: Binary
Relative target port: 0x7
designator type: Target port group, code set: Binary
Target port group: 0x1
designator type: NAA, code set: Binary
transport: Fibre Channel Protocol for SCSI (FCP-4)
0x267000c0ff267216
Target device that contains addressed lu:
designator type: NAA, code set: Binary
transport: Fibre Channel Protocol for SCSI (FCP-4)
0x208000c0ff267216
> If "sdc" and "sdd" are the same disk, the "Adressed logical unit" id should be
> the same for both.
So we have 0x600c0ff0001e91b2c1bae25601000000 twice, right?
There's a /dev/sdb as well, commented in fstab with "9750-8i Raid6
(4x3TB + 2x4TB)" but that seems another "branch" of devices:
# /usr/bin/sg_vpd --page=di /dev/sdb
Device Identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x600605b00d0ce810217ccffe19f851e8
-
In the first week of september I travel there and I have the job to
reinstall that server using Debian Linux (yes, gentoo-users, I am
getting OT here ;-)).
next prev parent reply other threads:[~2019-08-14 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 19:28 [gentoo-user] multipath.conf : learning how to use Stefan G. Weichinger
2019-07-29 19:37 ` [gentoo-user] fibrechannel (was: multipath.conf ) Stefan G. Weichinger
2019-07-29 20:08 ` Stefan G. Weichinger
2019-08-14 6:36 ` [gentoo-user] multipath.conf : learning how to use J. Roeleveld
2019-08-14 8:14 ` Stefan G. Weichinger [this message]
2019-08-14 11:20 ` J. Roeleveld
2019-08-14 12:17 ` Stefan G. Weichinger
2019-08-14 18:20 ` J. Roeleveld
2019-08-16 17:42 ` [EXTERNAL] " Laurence Perkins
2019-08-19 13:29 ` Stefan G. Weichinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38401489-dffa-b3e8-422f-3d3585ae74ad@xunil.at \
--to=lists@xunil.at \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox