From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
Chuck Lever <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: whither NFS umount?
Date: Wed, 13 Oct 2010 15:31:27 -0400 [thread overview]
Message-ID: <4CB6090F.60301@RedHat.com> (raw)
In-Reply-To: <20101013145601.468acc2a-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
On 10/13/2010 02:56 PM, Jeff Layton wrote:
> On Wed, 13 Oct 2010 14:45:57 -0400
> Steve Dickson <SteveD@redhat.com> wrote:
>
>> I would say send the UMNT, since it does not cause any pain to send it
>> verses the pain that could be cause by not sending it...
>>
>> This is a perfect example of fixing something that is not
>> broken... We can put our energy in better place that worrying
>> about things like this... IMHO...
>
> But it *is* broken. As Chuck pointed out, the main problem is that mtab
> handling is broken on remounts. That's a real problem that needs to be
> fixed.
Fine... Lets just focus on that issue...
>
> I agree that our time is better spent elsewhere. I just think that we
> ought to make that happen by eliminating the unnecessary umount helper.
> The less code that we need to maintain, the better...
In general I agree... but removing functionality (i.e. umount.nfs)
can cause more pain than just leaving things as is...
steved.
next prev parent reply other threads:[~2010-10-13 19:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 16:29 whither NFS umount? Chuck Lever
2010-10-12 17:04 ` Trond Myklebust
[not found] ` <1286903046.24878.13.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-10-12 17:57 ` Chuck Lever
2010-10-12 19:18 ` Jeff Layton
2010-10-12 19:44 ` Trond Myklebust
2010-10-12 19:52 ` Jeff Layton
2010-10-12 19:59 ` Chuck Lever
2010-10-12 20:21 ` Trond Myklebust
2010-10-12 20:26 ` Jeff Layton
2010-10-12 20:34 ` Chuck Lever
2010-10-12 20:50 ` Jeff Layton
2010-10-12 21:19 ` Chuck Lever
2010-10-13 1:00 ` Jeff Layton
2010-10-13 17:40 ` Steve Dickson
2010-10-13 18:13 ` Jeff Layton
2010-10-13 18:45 ` Steve Dickson
[not found] ` <4CB5FE65.3090409-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-10-13 18:56 ` Jeff Layton
2010-10-13 18:58 ` Jeff Layton
[not found] ` <20101013145601.468acc2a-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2010-10-13 19:31 ` Steve Dickson [this message]
2010-10-13 20:47 ` Chuck Lever
2010-10-13 23:19 ` Steve Dickson
2010-10-14 15:29 ` Chuck Lever
2010-10-14 18:27 ` Steve Dickson
2010-10-14 19:13 ` Chuck Lever
2010-10-14 21:24 ` Steve Dickson
2010-10-14 22:22 ` Chuck Lever
2010-10-15 13:11 ` Steve Dickson
2010-10-15 13:41 ` Jeff Layton
2010-10-15 16:00 ` Chuck Lever
2010-10-15 20:08 ` Steve Dickson
2010-10-18 15:18 ` Chuck Lever
2010-10-13 18:18 ` Trond Myklebust
2010-10-13 19:28 ` Steve Dickson
2010-10-14 14:00 ` J. Bruce Fields
2010-10-14 14:17 ` Trond Myklebust
[not found] ` <1287065841.3015.233.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-10-14 14:34 ` J. Bruce Fields
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=4CB6090F.60301@RedHat.com \
--to=steved@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).