Re: NFSv4 issue with netapp filer

On Thu, Oct 1, 2009 at 7:24 AM, Nathan Patwardhan <noopy.org <at> gmail.com> wrote:
> On Thu, Oct 1, 2009 at 5:12 AM, Guillaume Rousse
> <Guillaume.Rousse <at> inria.fr> wrote:
>> Nathan Patwardhan a écrit :
>>>
>>> On Wed, Sep 30, 2009 at 12:28 PM, Trond Myklebust
>>> <trond.myklebust <at> fys.uio.no> wrote:
>>>>
>>>> On Wed, 2009-09-30 at 18:05 +0200, Guillaume Rousse wrote:
>>>>>
>>>>> This seems to match the 'v4 server returned a bad sequence-id error on
>>>>> an unconfirmed sequence f5462f44!' in client logs.
>>>>
>>>> This is clearly a server bug. The client is allowed to use whatever
>>>> sequence id it likes for an OPEN with an unconfirmed open owner. I
>>>> thought this bug had been fixed in OnTap, though. Are you running the
>>>> latest version?
>>>
>>> I can confirm this still happens under OnTap 7.3.1 and NetApp has
>>> confirmed the bug (filed a Sev 2 ticket awhile back about it).  It
>>> appears that it's related to memory count on the filer and cannot be
>>> tuned in OnTap.
>>
>> Can you give me the bug number ? I can't find it on netapp bug tracking
>> system.
>
> Funny you should ask.  I just got a response from NetApp last night.
> The bug ID is 276821.

Also, FWIW, run 'lock status -n' when this situation happens and count
the number of NFSv4 locks.  If they are high, they can be cleared
under 7.3.X with 'lock break -p nfsv4 -h ip.of.offending.client.here'.
 I don't advise this as a course of practice but if you're in a pinch
it will make the resource errors disappear in the short term (until
they appear again).

--

-- 
Nathan Patwardhan