From: Franck Eyraud <franck+linux-cifs-ici3nDnK79kZQKRGMNo+Zg@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: DFS referrals support ?
Date: Fri, 12 Dec 2014 12:51:49 +0100 [thread overview]
Message-ID: <548AD6D5.7080901@nospam.yrnm.net> (raw)
Hi,
We are meeting some issues with DFS referrals when using CIFS for linux.
I don't know much about technical details on DFS, but before studying
further, I would like to know if this feature is even supposed to be
supported by the Linux CIFS client.
To explain the situation, we have several shares :
\\filer\main(main entry point)
\\filer\share1(scattered volumes with data)
\\filer\share2
if \\filer\main\share1points to \\filer\share1(top level) we manage to
access the share1 content correctly (so DFS mechanism seems to work)
but if \\filer\main\some\directory\remote\locationpoints to
\\filer\share2\dir1\dir2\inside\locationhere we get stuck.
The client can have the following behaviours, more or less with no
apparent logic up to now :
* "Object is remote" error
* "No such file or directory" error
* sometimes locked in infinite loop (with the older versions, see below)
* accesses it, but lists the content of \\filer\share2(top level of
the share) not the content of \\filer\share2\dir1\dir2\inside\locationso
we loose part of the link's path
With Windows 7 clients, the expected behaviour occurs correctly.
We use up-to-date debian 6.0.10 & 7.6, and CentOS 6.5 (i.e kernels
2.6.32 & 3.2.x) with stock cifs-utils package (2:4.5-2, 2:5.5-1) and the
CIFS server is NetApp OnTap 8, with the widelink feature (translation of
linux symlinks)
If this should be supported, can you provide information of the
parameters to set correctly, or if we have to compile a newer version,
which one ?
Thank you,
Franck
next reply other threads:[~2014-12-12 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 11:51 Franck Eyraud [this message]
[not found] ` <548AD6D5.7080901-ici3nDnK79kZQKRGMNo+Zg@public.gmane.org>
2014-12-12 19:50 ` DFS referrals support ? 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
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=548AD6D5.7080901@nospam.yrnm.net \
--to=franck+linux-cifs-ici3ndnk79kzqkrgmno+zg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox