All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: SteveD@redhat.com, Trond.Myklebust@netapp.com,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vivek Trivedi <vtrivedi018@gmail.com>
Subject: Re: [PATCH] nfs-util: Add cache_flush in mountd UMNT procedure.
Date: Wed, 11 Jul 2012 13:10:53 +0900	[thread overview]
Message-ID: <CAKYAXd97ir=tvxWTC4eVmrrXBEpK=XCX3-e8XUjCPy16eHoibQ@mail.gmail.com> (raw)
In-Reply-To: <20120710145937.GA1947@fieldses.org>

2012/7/10, J. Bruce Fields <bfields@fieldses.org>:
> On Sat, Jul 07, 2012 at 11:17:39PM -0400, Namjae Jeon wrote:
>> For removing storage device - user needs to safely un-mount the device
>> and then eject. But if 'EBUSY' occurs in umount then it will create
>> confusion for the user as it will mean some I/O is in progress - and
>> won't allow user to safely ejecting device.
>
Hi James.
> The one drawback is that recovering from the cache flushes might be a
> little expensive if you have a lot of exports in use.
Good point. I will look for more there is the method flush only mount entry.
>
> I'm curious, since you said this was for a usb disk: are users expected
> to just unplug it (in which case--is it read only?) or do they have some
> way of unmounting before they pull the plug?
Users expected to unplug it on both read only and read/write.
And there is no way that system be prepared to know about the
intelligence when the user is going to unplug.
if the user really want to detach the device safely. There is an
option like the desktop PC - where, we can say - umount/eject the
device. There is a proper user interface for safe removal.
but they can not unplug safely if usb device is mounted with nfs
because of this issue.
>
> --b.
>

  reply	other threads:[~2012-07-11  4:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08  3:17 [PATCH] nfs-util: Add cache_flush in mountd UMNT procedure Namjae Jeon
2012-07-10 14:59 ` J. Bruce Fields
2012-07-11  4:10   ` Namjae Jeon [this message]
2012-07-11 14:09     ` J. Bruce Fields
2012-07-11 22:38       ` Namjae Jeon
2012-07-11 22:43         ` Namjae Jeon
2012-07-24 16:24           ` J. Bruce Fields
2012-07-28  4:52             ` Namjae Jeon

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='CAKYAXd97ir=tvxWTC4eVmrrXBEpK=XCX3-e8XUjCPy16eHoibQ@mail.gmail.com' \
    --to=linkinjeon@gmail.com \
    --cc=SteveD@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=vtrivedi018@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.