Linux NFS development
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: "Shawn Lu (shawlu)" <shawlu@cisco.com>
Cc: Joshua Watt <jpewhacker@gmail.com>,
	"trond.myklebust@primarydata.com"
	<trond.myklebust@primarydata.com>,
	"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
	"jlayton@poochiereds.net" <jlayton@poochiereds.net>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Is "unmount -f"  worked as expected?
Date: Thu, 31 May 2018 15:28:20 -0400	[thread overview]
Message-ID: <20180531192820.GB3557@fieldses.org> (raw)
In-Reply-To: <D009E9C8-FB2B-4D93-BD91-EB4B47FCA983@cisco.com>

On Thu, May 31, 2018 at 06:04:52PM +0000, Shawn Lu (shawlu) wrote:
>  Yes, This will a big issue for cross mount.  Luckily, we have not
>  experience it yet due to low traffic.  
> 
>  By the way,  what is your suggestion on the road to enhance “umount
>  –f” ?   Will add kernel config option to support guaranteed force
>  unmount helps?

I honestly haven't been following that discussion.  If I were going to
work on this I'd start by studying the previous discussion that Joshua
references.

--b.

  reply	other threads:[~2018-05-31 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  0:38 Is "unmount -f" worked as expected? Shawn Lu (shawlu)
2018-05-30 13:44 ` Joshua Watt
2018-05-31 15:14   ` Shawn Lu (shawlu)
2018-05-31 15:18     ` bfields
2018-05-31 16:51       ` Shawn Lu (shawlu)
2018-05-31 17:34         ` bfields
2018-05-31 18:04           ` Shawn Lu (shawlu)
2018-05-31 19:28             ` bfields [this message]
2018-05-31 20:14               ` Shawn Lu (shawlu)
2018-05-31 18:44           ` Shawn Lu (shawlu)

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=20180531192820.GB3557@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=anna.schumaker@netapp.com \
    --cc=jlayton@poochiereds.net \
    --cc=jpewhacker@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=shawlu@cisco.com \
    --cc=trond.myklebust@primarydata.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