All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Question on IPv6 failover.
Date: Thu, 03 Oct 2013 16:08:01 -0700	[thread overview]
Message-ID: <524DF8D1.6000503@candelatech.com> (raw)
In-Reply-To: <CAH2r5mtirrcvkqQho7QvMDJ8eZWGT5Q2S9w=GLKuGiwM1z29GQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 10/03/2013 03:30 PM, Steve French wrote:
> On Thu, Oct 3, 2013 at 4:04 PM, Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org> wrote:
>> One of our users is reporting that the CIFS failover case is not working
>> properly.  They have a cluster of CIFS servers that migrate an IPv6 addr
>> to the active system.
>>
>> Evidently, our client-side CIFS connection follows the first migration,
>> but fails to go back to the original on a second failover.
>>
>> It could be any number of things, but I wanted first to see if anyone
>> knows how long client-side CIFS will keep attempting to regain contact with
>> it's
>> server?  Forever?
>>
>> Thanks,
>> Ben
>
> Depends on kernel version and also hard vs. soft (default) mount options.
>
> The "smb echo" approach that cifs moved to a few years ago allows
> the cifs kernel client to notice more quickly that the server is down,
> and significantly improved failover.
>
> Which kernel version?

3.7.10

The hard v/s soft is not being specified when mounting unless the
customer did something interesting, so I guess it is soft.

I'm still waiting on a network dump, so at this time I have no
reason to believe that Linux CIFS is actually to blame...just
trying to understand the possibilities better.

Thanks,
Ben

-- 
Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org>
Candela Technologies Inc  http://www.candelatech.com

  parent reply	other threads:[~2013-10-03 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 21:04 Question on IPv6 failover Ben Greear
     [not found] ` <524DDBF7.5050709-my8/4N5VtI7c+919tysfdA@public.gmane.org>
2013-10-03 22:30   ` Steve French
     [not found]     ` <CAH2r5mtirrcvkqQho7QvMDJ8eZWGT5Q2S9w=GLKuGiwM1z29GQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-03 23:08       ` Ben Greear [this message]
2013-10-04  1:41   ` Jeff Layton

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=524DF8D1.6000503@candelatech.com \
    --to=greearb-my8/4n5vti7c+919tysfda@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@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.