[Bug 1013724] Re: Setting prio const in multipath.conf has no effect

2012-07-10 Thread Vassilis Vatikiotis
multipath.conf follows. The file is heavily commented so I trimmed all comments out defaults { user_friendly_names yes } blacklist { devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[-1-9]* devnode ^hd[a-z][[0-9]*] wwid 3600508b1001cea3b91ee45c710e467a7 #sda

[Bug 1013724] Re: Setting prio const in multipath.conf has no effect

2012-07-10 Thread Peter Petrakis
If your device is mounted, you won't be able to flush it, flush == destroy. OK. so it's not just you, I can recreate this. Coincidentally, I also have an HP RAID controller and see the same warning message. This device *is blacklisted* but apparently it's still getting probed. Shouldn't be

[Bug 1013724] Re: Setting prio const in multipath.conf has no effect

2012-07-10 Thread Vassilis Vatikiotis
multipath.conf follows. The file is heavily commented so I trimmed all comments out defaults { user_friendly_names yes } blacklist { devnode ^(ram|raw|loop|fd|md|dm-|sr|scd|st)[-1-9]* devnode ^hd[a-z][[0-9]*] wwid 3600508b1001cea3b91ee45c710e467a7 #sda

[Bug 1013724] Re: Setting prio const in multipath.conf has no effect

2012-07-10 Thread Peter Petrakis
If your device is mounted, you won't be able to flush it, flush == destroy. OK. so it's not just you, I can recreate this. Coincidentally, I also have an HP RAID controller and see the same warning message. This device *is blacklisted* but apparently it's still getting probed. Shouldn't be

[Bug 1013724] Re: Setting prio const in multipath.conf has no effect

2012-07-09 Thread Peter Petrakis
Please provide the entire multipath.conf file, in the meanwhile try stopping the daemon, perform a table flush (multipath -F) , then simply run multipath -v4 (no daemon) and observe the results. ** Changed in: multipath-tools (Ubuntu) Status: New = Incomplete ** Changed in:

[Bug 1013724] Re: Setting prio const in multipath.conf has no effect

2012-07-09 Thread Peter Petrakis
Please provide the entire multipath.conf file, in the meanwhile try stopping the daemon, perform a table flush (multipath -F) , then simply run multipath -v4 (no daemon) and observe the results. ** Changed in: multipath-tools (Ubuntu) Status: New = Incomplete ** Changed in:

[Bug 1013724] Re: Setting prio const in multipath.conf has no effect

2012-06-18 Thread Robie Basak
** Changed in: multipath-tools (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1013724 Title: Setting prio const in multipath.conf

[Bug 1013724] Re: Setting prio const in multipath.conf has no effect

2012-06-18 Thread Robie Basak
** Changed in: multipath-tools (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013724 Title: Setting prio const in multipath.conf has no effect To manage