On 11/08/2016 08:32 PM, Xose Vazquez Perez wrote:
NetApp did confirm this is only required for ONTAP(LUN C-Mode).
Cc: Martin George
Cc: Robert Stankey
Cc: Steven Schremmer
Cc: Sean Stewart
On 11/08/2016 07:52 PM, Xose Vazquez Perez wrote:
On 07/15/2016 08:48 AM, Hannes Reinecke wrote:
Recent kernels have an 'access_state' attribute which allows
us to read the asymmetric access state directly from sysfs.
Hi Hannes,
with this patch it's impossible to select/autodetect ALUA.
> "Mike" == Mike Snitzer writes:
Mike,
>> However, doesn't it make more sense to tweak limits on DM device
>> instead of the underlying ones? It seems a bit counter-intuitive to
>> me to change max_sectors_kb on a different device than the one where
>> the filesystem
I'm looking through the multipath udev rules again to see if we can come
closer to one consistent set, or at least understand why we need to
agree to disagree and right now I'm trying to figure out why it's
important for SUSE to have 56-multipath.rules run before
60-persistent-storage.rules.
We
NetApp did confirm this is only required for ONTAP(LUN C-Mode).
Cc: Martin George
Cc: Robert Stankey
Cc: Steven Schremmer
Cc: Sean Stewart
Cc: Hannes Reinecke
Cc:
On 07/15/2016 08:48 AM, Hannes Reinecke wrote:
> Recent kernels have an 'access_state' attribute which allows
> us to read the asymmetric access state directly from sysfs.
Hi Hannes,
with this patch it's impossible to select/autodetect ALUA.
sysfs always takes precedence over alua.
On Tue, Nov 08, 2016 at 11:05:01AM +0800, tang.wenj...@zte.com.cn wrote:
Thanks.
ACK
-Ben
> From: 10144149
>
> Deadlock occurred in uev_add_path() when >lock would lock twice in
> uev_update_path()
> ---
> multipathd/main.c | 54