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 14:17:23 +0200 [thread overview]
Message-ID: <50ccc42a-ec35-2583-98f5-c175a8ac3fec@xunil.at> (raw)
In-Reply-To: <1786455.n5vAsDlxU6@andromeda>
Am 14.08.19 um 13:20 schrieb J. Roeleveld:
> If there is no documentation, it is a mess by definition.
yes :-)
>>>> 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 ...
>
> See next item, make sure you do NOT mount both at the same time.
I understand and agree ;-)
>> # /usr/bin/sg_vpd --page=di /dev/sdb
>> Device Identification VPD page:
>> Addressed logical unit:
>> designator type: NAA, code set: Binary
>> 0x600605b00d0ce810217ccffe19f851e8
>
> Yes, this one is different.
>
> I checked the above ID and it looks like it is already correctly configured.
> Is " multipathd " actually running?
no!
> If it were running correctly, you would mount " /dev/mapper/.... " instead of
> " /dev/sdc " or " /dev/sdd ".
>
>> 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 ;-)).
>
> For something that doesn't get updated/managed often, Gentoo might not be the
> best choice, I agree.
> I would prefer Centos for this one though, as there is far more info on
> multipath from Redhat.
I will consider this ...
As I understand things here:
the former admin *tried to* setup multipath and somehow got stuck.
That's why it isn't running and not used at all. He somehow mentioned
this in an email back then when he was still working there.
So currently it seems to me that the storage is attached via "single
path" (is that the term here?) only. "directly"= no redundancy
That means using the lpfc-kernel-module to run the FibreChannel-adapters
... which failed to come up / sync with a more recent gentoo kernel, as
initially mentioned.
(right now: 4.1.15-gentoo-r1 ... )
I consider sending a Debian-OS on a SSD there and let the (low
expertise) guy there boot from it. (or a stick). Which in fact is risky
as he doesn't know anything about linux.
Or I simply wait for my on-site-appointment and start testing when I am
there.
Maybe I am lucky and the debian lpfc stuff works from the start. And
then I could test multipath as well.
I assume that maybe the adapters need a firmware update or so.
-
The current gentoo installation was done with "hardened" profile, not
touched for years, no docs .... so it somehow seems way too much hassle
to get it up to date again. Additionally no experts on site there, so it
should be low maintenance anyway.
next prev parent reply other threads:[~2019-08-14 12:17 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
2019-08-14 11:20 ` J. Roeleveld
2019-08-14 12:17 ` Stefan G. Weichinger [this message]
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=50ccc42a-ec35-2583-98f5-c175a8ac3fec@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