linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Malahal Naineni <malahal@us.ibm.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] umount.nfs: normalize path names during umounts.
Date: Mon, 05 Mar 2012 21:38:16 -0500	[thread overview]
Message-ID: <4F557898.7040002@RedHat.com> (raw)
In-Reply-To: <20120306022505.GA32281@us.ibm.com>



On 03/05/2012 09:25 PM, Malahal Naineni wrote:
> Jim Rees [rees@umich.edu] wrote:
>> I don't understand the backward compatibility issue.  Are there times when
>> you have a mount, and it's in /etc/mtab, but not in /proc/mounts?  I don't
>> see how that's possible.
> 
> No, but that is what NFS umount thinks due to slight differences in
> those two files. Happens only in NFSv4 world. 
Exactly... When /etc/mtab and /proc/mounts are not symbolically 
linked the v4 mount are written differently to both files as 
well as v3 mount are also written differently that v4 mounts...

steved.


  reply	other threads:[~2012-03-06  2:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 19:36 [PATCH 0/1] Normalized path names on umounts (take 2) Steve Dickson
2012-03-05 19:36 ` [PATCH 1/1] umount.nfs: normalize path names during umounts Steve Dickson
2012-03-05 21:20   ` Malahal Naineni
2012-03-05 21:30     ` Malahal Naineni
2012-03-06  0:28       ` Steve Dickson
2012-03-06  0:27     ` Steve Dickson
2012-03-06  0:31       ` Myklebust, Trond
2012-03-06  0:53         ` Steve Dickson
2012-03-06  1:04           ` Myklebust, Trond
2012-03-06  1:35             ` Steve Dickson
2012-03-06  1:52               ` Jim Rees
2012-03-06  2:25                 ` Malahal Naineni
2012-03-06  2:38                   ` Steve Dickson [this message]
2012-03-05 19:37 ` [PATCH 0/1] Normalized path names on umounts (take 2) Chuck Lever
2012-03-05 19:44   ` 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=4F557898.7040002@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=malahal@us.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).