From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Cc: eric2.valette-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org,
donald.r.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Linux 3.2.17 and netapp 8.1
Date: Tue, 15 May 2012 19:15:21 +0530 [thread overview]
Message-ID: <4FB25DF1.9080402@suse.com> (raw)
In-Reply-To: <20120515090907.39197340-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
On 05/15/2012 06:39 PM, Jeff Layton wrote:
> On Tue, 15 May 2012 09:20:14 +0200
> VALETTE Eric RD-MAPS-REN <eric2.valette-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org> wrote:
>
>> On 05/14/2012 07:15 PM, Jeff Layton wrote:
>>>
>>> BTW: I've seen prototype SMB2 support in git tress pushed in october.
>>> Any plan to submit something upstream?
>>>
>>> Thanks for your support,
>>>
>>>
>>> Yes, we're working on it. I think we've come to some consensus on a
>>> basic design and I believe Pavel is now working to forward-port the
>>> previous patches to that design.
>>>
>> OK. Will wait then. Any chance it might helps with the netapp?
>>
>>> In Netapps defense Ontap 8.1 is an early release which are known to be buggy.
>> Well its been released around february if google can be trusted and what
>> this says is that netapp don't care about Linux support at all and do
>> not even perform basic test with linux client. I'm rather sure we asked
>> about linux compatibility before moving from 7.xx to 8.01.
>>
>> -- eric
>>
>
> For the record...
>
> The story I've heard in the past (albeit second or third hand) is that
> Netapp is not interested in interop with non-windows clients. It's
Yeah, I have heard similar stories too and from what I have heard from
the NetApp customers, NetApp seems to strongly suggest to use _only_ NFS
with the Linux clients.
Thanks
Suresh
prev parent reply other threads:[~2012-05-15 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 12:43 Linux 3.2.17 and netapp 8.1 VALETTE Eric RD-MAPS-REN
[not found] ` <4FB0FDDA.5080604-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org>
2012-05-14 16:01 ` Jeff Layton
[not found] ` <20120514120159.2f6de2fa-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-05-14 16:06 ` VALETTE Eric RD-MAPS-REN
[not found] ` <4FB12D71.3040403-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org>
2012-05-14 16:18 ` Jeff Layton
[not found] ` <20120514121824.273198a9-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-05-14 16:23 ` VALETTE Eric RD-MAPS-REN
[not found] ` <4FB13173.1070509-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org>
2012-05-14 17:15 ` Jeff Layton
[not found] ` <20120514131559.7ca0cdc4-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-05-14 19:04 ` Don Gray
2012-05-15 7:20 ` VALETTE Eric RD-MAPS-REN
[not found] ` <4FB203AE.3020408-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org>
2012-05-15 13:09 ` Jeff Layton
[not found] ` <20120515090907.39197340-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2012-05-15 13:29 ` VALETTE Eric RD-MAPS-REN
2012-05-15 13:45 ` Suresh Jayaraman [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=4FB25DF1.9080402@suse.com \
--to=sjayaraman-ibi9rg/b67k@public.gmane.org \
--cc=donald.r.gray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=eric2.valette-C0LM0jrOve7QT0dZR+AlfA@public.gmane.org \
--cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@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