Thanks Justin,

That's really unfortunate. However, this explains more of what I saw in the tcpdump  We will open a case and ask to be added to that bug. 

I don't think our customers are going to take too kindly to the idea of having to purchase a third party client. It seems like our only option is to move them back to 7mode and re-evaluate our path forward. 

--
Mike Garrison
University of Michigan



On Tue, Mar 25, 2014 at 9:40 PM, Parisi, Justin <Justin.Parisi@netapp.com> wrote:
There is no Windows NFS support with cDOT for the native NFS client yet.
The issue is that Windows NFS uses non-monitored locks, which cDOT does
not support currently. There are plans to add this support to future
releases.

You have options, however.

Hummingbird/OpenText offers an NFS client that will work with cDOT in the
following scenarios:

- Disabling NLM over NFSv3
- Using NFSv4 (this will require some LDAP server for identity mapping to
work properly)

I'd suggest opening a support case and having the engineer add the case
number to bug 296324.

http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=296324


On 3/25/14 6:08 PM, "Ray Van Dolson" <rvandolson@esri.com> wrote:

>Nice.  How the heck does the filer differentiate between the Windows
>NFSv3 client and a Unix NFSv3 client I wonder?
>
>On Tue, Mar 25, 2014 at 06:02:47PM -0400, Michael Garrison wrote:
>> Sadly, Windows doesn't let you specify a version! However, NetApp CDot
>>doesn't
>> support NFS v3 windows client like 7mode does. Just discovered this in
>>release
>> notes:
>>
>> "Windows NFSv3 clients not supported in clustered Data ONTAP
>> Although Data ONTAP supports both the NFS and SMB file access
>>protocols, file
>> access over
>> NFSv3 from Windows clients is currently only supported in Data ONTAP
>>operating
>> in 7-Mode; it is
>> not supported in clustered Data ONTAP.
>> If your environment requires Windows clients to be able to access the
>>storage
>> system over NFSv3,
>> you should not upgrade to clustered Data ONTAP."
>>
>> Awesome.
>>
>> --
>> Mike Garrison
>>
>>
>> On Tue, Mar 25, 2014 at 5:59 PM, Jordan Slingerland <
>> Jordan.Slingerland@independenthealth.com> wrote:
>>
>>     Try mount -t NFSv3
>>     ________________________________________
>>     From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net]
>>on
>>     behalf of Michael Garrison [mcgarr@umich.edu]
>>     Sent: Tuesday, March 25, 2014 5:45 PM
>>     To: toasters@teaparty.net
>>     Subject: CDOT 8.2p5, NFS w/ Win2012 or Win 7?
>>
>>     We recently migrated a bunch of NFS volumes from 7mode to a cdot
>>system.
>>     The CDot cluster has only NFSv3 enabled.  We have some Windows 7 and
>>     Windows 2012 machines that can no longer mount the NFS volumes.
>>
>>     No matter how they try it, they receive the following error:
>>
>>     C:\Windows\system32>mount -o nolock \\server\share Z:
>>     Network Error - 53
>>     Type 'NET HELPMSG 53' for more information.
>>
>>     Yet, the exact same mount parameters work fine on the 7mode share.
>>They've
>>     rebooted, tried multiple computers, and it's consistent behavior.
>>
>>     Is anyone else out there running CDot 8.2p5 and have any success
>>with Win7
>>     or Win2012 machines?
>>
>>     Thanks,
>>     Mike Garrison
>>     University of Michigan
>_______________________________________________
>Toasters mailing list
>Toasters@teaparty.net
>http://www.teaparty.net/mailman/listinfo/toasters