All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: fstests@vger.kernel.org, Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH] common/rc: Use -v option with findmnt
Date: Tue, 14 Mar 2017 13:07:39 +0800	[thread overview]
Message-ID: <20170314050739.GY14226@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170313180726.1967-1-rgoldwyn@suse.de>

On Mon, Mar 13, 2017 at 01:07:26PM -0500, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
> 
> Since btrfs puts in the subvol name in the device, we should
> use -v option to not print the bind mounts or btrfs volumes.
> 
> Fixes: 5e6892d ("common/rc: use findmnt to check mounted device")
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>

Hmm, I mounted a btrfs snapshot of TEST_DEV to another dir and ran
check, check reported:

TEST_DEV=/dev/sdc1 is mounted but not on TEST_DIR=/mnt - aborting
Already mounted result:
/dev/sdc1[/snap] /mnt/scratch

which seems fine and clear to me. Did you hit any particular failures
without this fix?

Thanks,
Eryu

> ---
>  common/rc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/common/rc b/common/rc
> index d53f679..d7a5321 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -1463,7 +1463,7 @@ _check_mounted_on()
>  	local type=$5
>  
>  	# find $dev as the source, and print result in "$dev $mnt" format
> -	local mount_rec=`findmnt -rnc -S $dev -o SOURCE,TARGET`
> +	local mount_rec=`findmnt -rncv -S $dev -o SOURCE,TARGET`
>  	[ -n "$mount_rec" ] || return 1 # 1 = not mounted
>  
>  	# if it's mounted, make sure its on $mnt
> -- 
> 2.10.2
> 

  reply	other threads:[~2017-03-14  5:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 18:07 [PATCH] common/rc: Use -v option with findmnt Goldwyn Rodrigues
2017-03-14  5:07 ` Eryu Guan [this message]
2017-03-14 14:07   ` Goldwyn Rodrigues
2017-03-15  8:44     ` Eryu Guan

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=20170314050739.GY14226@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=rgoldwyn@suse.com \
    --cc=rgoldwyn@suse.de \
    /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.