From: "Victoria A Smith" <vasmith@sandia.gov>
To: dm-devel@redhat.com
Subject: Re: bindings file; rename WWID to mpath alias
Date: Mon, 26 Apr 2010 15:13:09 -0600 [thread overview]
Message-ID: <4BD601E5.6060705@sandia.gov> (raw)
In-Reply-To: <1272322814.16254.14.camel@localhost>
It is on /var (/var/lib/multipath/bindings), and /var is a separate LV
from /.
I am beginning to think the WWID 350002ac002c506cc is a "rogue" device
and should be removed from the system.
Regards,
Victoria
brem belguebli said the following on 04/26/2010 05:00 PM:
> Is your bindings file located on a different [lv|partition] than / ?
>
> It may cause this kind of troubles if so.
>
> Brem
>
> On Mon, 2010-04-26 at 13:58 -0600, Victoria A Smith wrote:
>
>> After a system crash I have filesystem access problems when
>> the multipathd service is started. I noticed in the messages file
>> and in output from multipath -ll that an alias is not being
>> used:
>>
>> messages: [...] rename 350002ac002c506cc to mpath18
>>
>> # multipath -ll
>> [...]
>> 350002ac002c506cc dm-12 3PARdata,VV
>>
>> # ls -1 /dev/mpath/
>> 350002ac002c506cc
>> mpath10
>> [...]
>>
>>
>> The bindings file has:
>> [...]
>> mpath18 350002ac002c506cc
>>
>>
>> Can the apparent failure of the alias-to-WWID mapping cause any problems?
>>
>>
>> RHEL5.5
>> 2.6.18-194.el5
>> device-mapper-multipath-0.4.7-34.el5
>> QLogic Fibre Channel HBA Driver: 8.03.01.04.05.05-k
>>
>>
>> Thanks,
>>
>> Victoria
>>
>>
>> --
>> dm-devel mailing list
>> dm-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/dm-devel
>>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
next prev parent reply other threads:[~2010-04-26 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 19:58 bindings file; rename WWID to mpath alias Victoria A Smith
2010-04-26 23:00 ` brem belguebli
2010-04-26 21:13 ` Victoria A Smith [this message]
2010-04-26 23:56 ` brem belguebli
2010-04-26 22:21 ` Victoria A Smith
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=4BD601E5.6060705@sandia.gov \
--to=vasmith@sandia.gov \
--cc=dm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.