From: Alex Bligh <alex-rWA27mgs/Jz10XsdtD+oqA@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: cifs.ko client failover with CSVFS Windows 2012 R2 server
Date: Tue, 23 Jun 2015 12:54:23 +0100 [thread overview]
Message-ID: <558948EF.9010008@alex.org.uk> (raw)
I'm trying to establish to what extent a cifs.ko linux client will
support failover with a Windows 2012 R2 server, sharing a CSVFS
backend. The symptom a user is seeing here is that the share
works, but the file system does not fail over if the server it
initially mounts goes down (kernel 3.13.0-49-generic, on
Ubuntu 14.04).
This link:
https://wiki.samba.org/index.php/SMB3_kernel_status#Witness_Notification_Protocol
implies that Witness Notification Protocol should work for a
client if vers=3.02 is passed to mount.cifs. However, the user
seems unable to get failover to work at all (transparently or
otherwise).
Questions:
* Is failover supported on cifs.ko, and if so do I need a newer
kernel version than 3.13? Are there any special commands needed
to enable it other than mounting with vers=3?
* Is transparent failover supported on cifs.ko, and do I need
need a newer version than 3.13? Are there areny special commands
needed to enable it other than mounting with vers=3.02?
* Is there a 'HOWTO' to debug this? It seems to be hard to search
for client stuff that works with failover.
--
Alex Bligh
next reply other threads:[~2015-06-23 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 11:54 Alex Bligh [this message]
[not found] ` <558948EF.9010008-rWA27mgs/Jz10XsdtD+oqA@public.gmane.org>
2015-06-23 15:17 ` cifs.ko client failover with CSVFS Windows 2012 R2 server Steve French
[not found] ` <CAH2r5muVBQ3OKrV8o466PwMWSh_SSbjkbM+KDPAqPXL0qx6VEA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-23 19:20 ` Alex Bligh
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=558948EF.9010008@alex.org.uk \
--to=alex-rwa27mgs/jz10xsdtd+oqa@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.