From: Franck Eyraud <franck+linux-cifs-ici3nDnK79kZQKRGMNo+Zg@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: DFS referrals support ?
Date: Fri, 13 Mar 2015 17:07:11 +0100 [thread overview]
Message-ID: <55030B2F.5090507@nospam.yrnm.net> (raw)
In-Reply-To: <CAH2r5mtOtmhEMgGOq22fy-RQa58c+u=JWwfGOvXh83MyZwb4og-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Le 09/01/2015 20:51, Steve French a écrit :
> What did you find out about behavior of a more current kernel? (given
> that your kernel was more than 5 years old, there is a good chance
> that the behavior has improved in more recent kernels)
Sorry for long delay answer, but this issue was put aside as not
critical (first choice to access the filer from Linux clients is NFS).
Unfortunately we could not for technical/schedule reasons test other
kernels.
However, it seems that after a recent upgrade on the NetApp filer to
OnTap 8.2.3 this behaviour disappeared from all our systems. So it seems
a case of faulty server, and not linked to Linux CIFS client.
Have a good day, and thanks for support.
Franck
prev parent reply other threads:[~2015-03-13 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 11:51 DFS referrals support ? Franck Eyraud
[not found] ` <548AD6D5.7080901-ici3nDnK79kZQKRGMNo+Zg@public.gmane.org>
2014-12-12 19:50 ` Bob Balsover
[not found] ` <dda8f4838ed40871acc3092c5440d396.squirrel-vQd1aa0lCeAC/Zx7Cl00UAC/G2K4zDHf@public.gmane.org>
2014-12-13 9:35 ` Franck Eyraud
[not found] ` <548C086C.8050102-ici3nDnK79kZQKRGMNo+Zg@public.gmane.org>
2015-01-09 19:51 ` Steve French
[not found] ` <CAH2r5mtOtmhEMgGOq22fy-RQa58c+u=JWwfGOvXh83MyZwb4og-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-13 16:07 ` Franck Eyraud [this message]
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=55030B2F.5090507@nospam.yrnm.net \
--to=franck+linux-cifs-ici3ndnk79kzqkrgmno+zg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox