From: Steve Dickson <SteveD@redhat.com>
To: NeilBrown <neilb@suse.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] mount.nfs - hide EBUSY errors.
Date: Wed, 16 Mar 2016 14:19:12 -0400 [thread overview]
Message-ID: <56E9A3A0.40002@RedHat.com> (raw)
In-Reply-To: <877fi2raey.fsf@notabene.neil.brown.name>
On 02/17/2016 09:59 PM, NeilBrown wrote:
>
> Linux only returns EBUSY for a non-remount mount if the exact
> requested filesystem is already mounted. Arguably this is not an
> error.
>
> "mount -a" tries to see if each requested filesystem is already mounted.
> Sometimes it gets it wrong - e.g. hostname aliases can confuse it.
> So "mount -a" will report a failure "already mounted", which is
> wrong because it should filter those out.
>
> An easy fix it just to be silent about EBUSY. As the requested
> result (a given filesystem being mounted at a given location) is in
> effect after the EBUSY return, we can just treat it as success.
>
> This removes the confusing "already mounted" errors.
>
> Signed-off-by: NeilBrown <neilb@suse.com>
Committed...
steved.
> ---
> utils/mount/stropts.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/utils/mount/stropts.c b/utils/mount/stropts.c
> index 86829a902bfd..320dde2fab92 100644
> --- a/utils/mount/stropts.c
> +++ b/utils/mount/stropts.c
> @@ -960,6 +960,15 @@ static int nfsmount_fg(struct nfsmount_info *mi)
> if (nfs_try_mount(mi))
> return EX_SUCCESS;
>
> + if (errno == EBUSY)
> + /* The only cause of EBUSY is if exactly the desired
> + * filesystem is already mounted. That can arguably
> + * be seen as success. "mount -a" tries to optimise
> + * out this case but sometimes fails. Help it out
> + * by pretending everything is rosy
> + */
> + return EX_SUCCESS;
> +
> if (nfs_is_permanent_error(errno))
> break;
>
>
prev parent reply other threads:[~2016-03-16 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 2:59 [PATCH] mount.nfs - hide EBUSY errors NeilBrown
2016-03-16 18:19 ` Steve Dickson [this message]
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=56E9A3A0.40002@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.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.