From: Volker Lendecke <Volker.Lendecke-PS7XAnAlDA+VvDNblw4Uiw@public.gmane.org>
To: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Cc: lists-dLPT46B32WUjnolme5KbmQ@public.gmane.org,
samba-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Samba] cifs and Netapp DFS-shares problems
Date: Fri, 10 Dec 2010 12:52:59 +0100
Date: Fri, 10 Dec 2010 12:52:59 +0100 [thread overview]
Message-ID: <E1PR1i2-002xBc-Uw@intern.SerNet.DE> (raw)
In-Reply-To: <20101210063449.5ab06c5f-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
On Fri, Dec 10, 2010 at 06:34:49AM -0500, Jeff Layton wrote:
> You're welcome to open a bug at bugzilla.samba.org, cc me, and I'll
> take a look when I have time. Gathering wire captures during one of
> these events and attaching them to the bug would help to track down the
> problem. It's likely to be Netapp's bug however...
NetApp explicitly refuses to fix anything that is outside
their supported client matrix. I've heard that from NetApp
reps responsible for my customers. cifsfs is outside that
matrix. NetApp's fix is to tell people to use NFS when
coming from Linux.
Volker
next prev parent reply other threads:[~2010-12-10 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291855039.11237.49.camel@kramer>
[not found] ` <1291976746.8971.24.camel@kramer>
2010-12-10 11:34 ` cifs and Netapp DFS-shares problems Jeff Layton
[not found] ` <20101210063449.5ab06c5f-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-12-10 11:52 ` Volker Lendecke [this message]
2010-12-10 15:17 ` [Samba] " Steve French
2010-12-10 15:00 ` Marcus
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=E1PR1i2-002xBc-Uw@intern.SerNet.DE \
--to=volker.lendecke-ps7xanalda+vvdnblw4uiw@public.gmane.org \
--cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lists-dLPT46B32WUjnolme5KbmQ@public.gmane.org \
--cc=samba-w/Ol4Ecudpl8XjKLYN78aQ@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.