Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: V4 unmount causes a GETATTR
Date: Fri, 15 Feb 2013 16:45:47 -0500	[thread overview]
Message-ID: <511EAC8B.3050403@RedHat.com> (raw)
In-Reply-To: <20130215182531.GB19923@fieldses.org>



On 15/02/13 13:25, J. Bruce Fields wrote:
> On Fri, Feb 15, 2013 at 10:46:00AM -0500, Steve Dickson wrote:
>> Hello,
>>
>> I have not tracked down as to the exact reason, 
>> but it appears umount of v4 file system cause the
>> directory to be revalidating causing the  GETATTR. 
>>
>> Is this revalidation really necessary on an unmount? 
> 
> I don't know, maybe not.  But even if it's not, there are other things
> (like cleaning up state) that the client will likely try to do on
> unmount.  In the presence of delegations it could have dirty data that
> it's required to write back even if applications don't currently hold
> any open files.
Understood with dirty data... but what I as seeing was a v4 mount and
then a reboot with no activity on the mount point... 

> 
> So I don't think we can promise umount will work without the network.
Again with open files (aka activity on the mount point) I agree but
with no activity or open files, I'm think that GETATTR is simply not
necessary... 

steved.

  reply	other threads:[~2013-02-15 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 15:46 V4 unmount causes a GETATTR Steve Dickson
2013-02-15 18:25 ` J. Bruce Fields
2013-02-15 21:45   ` Steve Dickson [this message]
2013-02-16  5:17     ` Myklebust, Trond
2013-02-16 15:11       ` Steve Dickson

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=511EAC8B.3050403@RedHat.com \
    --to=steved@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.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