[SOLVED] Re: paths scsi names persistence after rescan

[Peter M. Petrakis]

On 06/02/2011 10:58 AM, bencer at cauterized.net wrote:
> On Wed, 01 Jun 2011 15:37:44 -0400, "Peter M. Petrakis"
> <peter.petrakis at canonical.com>  wrote:
>>
>> One thing that bugged me about your multipath.conf
>>
>> blacklist {
>>>      devnode "sda"
>>>      devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
>>>      devnode "^hd[a-z][[0-9]*]"
>>>      devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
>>> }
>>
>> I'd rather see:
>>
>> devnode "^sda[0-9]*"
>>
>> beyond that it looks OK.
>
> agreed, fixed.
>
>>
>> So to debug this we'll need to see:
>> - contents of /dev/disk
>> - udevadm monitor>  udev.log
>> - stop multipathd and run it in the foreground to capture logging
>
> http://paste.ubuntu.com/616565/
>
>> * service multipath-tools stop
>> * multipathd -v4 -d>  mpd.log
>
> http://paste.ubuntu.com/616561/
>
>>
>> You haven't modified or added any udev rules have you?
>> Also do you have anything like dmraid or LVM running?
>
> I run LVM: http://paste.ubuntu.com/616563/
>
> Thanks for you help!
>
>
To follow up:

https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/644489

This problem has been run down to multipath-tools and an SRU
is pending to address the issue from lucid-natty, oneiric is
unaffected. If you're a multipath user and you're seeing
a swath of unexplained UDEV CHANGE events from your path members,
the next update will solve your problem. Dropping the CHANGE
filter from the associated UDEV rules *is not* the answer.

An updated lucid multipath-tools is available from my ppa.

ppa:peter-petrakis/storage

Peter