The issue on this particular system is that the binding file resides
on /var which isn't available early enough for
/etc/init.d/multipath-tools-boot.
In that case the paths got assigned new names during each boot which
causes the problem.
A workaround is to use the multipath-tools-boot package
Tags 586182 +fixed-upstream
thanks
On Thu, Jun 17, 2010 at 05:19:00PM +1000, Vincent McIntyre wrote:
> Package: multipath-tools
> Version: 0.4.8-14+lenny2
> Severity: normal
>
> *** Please type your report below this line ***
>
> Sometimes, multipath-tools does not create all the /dev/mapper/mpa
On Thu, Jun 17, 2010 at 02:57:17PM +0530, Ritesh Raj Sarraf wrote:
> The maintainer for multipath-tools should be able to give you more
> information
> but in my experience, the friendly_names feature of multipath-tools have
> turned out to be more of a problem.
>
> I believe there is a bug tha
The maintainer for multipath-tools should be able to give you more information
but in my experience, the friendly_names feature of multipath-tools have
turned out to be more of a problem.
I believe there is a bug that talks about a locking issue with friendly_names
upstream.
In face, I have be
Package: multipath-tools
Version: 0.4.8-14+lenny2
Severity: normal
*** Please type your report below this line ***
Sometimes, multipath-tools does not create all the /dev/mapper/mpathN
devices one is expecting it to create. This seems to occur if there
more than two multipathed devices.
I have
5 matches
Mail list logo
