linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: Josef Bacik <jbacik@fusionio.com>, <dsterba@suse.cz>,
	<linux-btrfs@vger.kernel.org>, <chris.mason@fusionio.com>
Subject: Re: [PATCH 1/3 v4] btrfs-progs: use kernel for mounted disk for show
Date: Tue, 22 Oct 2013 09:21:47 -0400	[thread overview]
Message-ID: <20131022132147.GA27304@localhost.localdomain> (raw)
In-Reply-To: <526612EB.1050802@oracle.com>

On Tue, Oct 22, 2013 at 01:53:47PM +0800, Anand Jain wrote:
> 
> 
> On 10/21/13 10:44 PM, Josef Bacik wrote:
> >On Tue, Oct 15, 2013 at 07:13:33PM +0200, David Sterba wrote:
> >>On Tue, Oct 08, 2013 at 11:41:38AM +0800, Anand Jain wrote:
> >>>As of now btrfs filesystem show reads directly from
> >>>disks. So sometimes output can be stale, mainly when
> >>>user wants to cross verify their operation like,
> >>>label or device delete or add... etc. so this
> >>>patch will read from the kernel ioctl if it finds
> >>>that disk is mounted.
> >>
> >>Sorry for holding this patch back for so long, I wanted to find out why
> >>the output is different before and after. The reason is simple, for my
> >>convenience I've added the user to the 'disk' group so I can access the
> >>block devices without root. This patch stops to read the block devs
> >>directly and uses the ioctl BTRFS_IOC_FS_INFO which gives me a silent
> >>EPERM. If I run show with sudo, then all filesystems show up as
> >>expected.
> >>
> >
> >This patch needs to be dropped (I imagine the whole series too) as it breaks
> >xfstests btrfs/003.  If I do btrfs fi show on a mounted fs I get this
> >
> >[root@destiny btrfs-progs]# btrfs fi show /dev/sdc
> >Btrfs v0.20-rc1-483-ge0173f6
> >[root@destiny btrfs-progs]#
> >
> >Chris this is in integration, so maybe a revert?  Thanks,
> 
>  That would be less productive approach as a whole.
>  I have sent out the fix for this. Kindly find it.
> 
> ---
> [PATCH 1/2] btrfs-progs: make get_btrfs_mount callable
> [PATCH 2/2] btrfs-progs: filesystem show of specified mounted disk should
> work
> ---
> 

Did you test these?  Because they aren't working for me, so I think a revert is
the only solution.  Thanks,

Josef

  reply	other threads:[~2013-10-22 13:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  3:41 [PATCH 1/3 v4] btrfs-progs: use kernel for mounted disk for show Anand Jain
2013-10-08  3:41 ` [PATCH 2/3 v2] btrfs-progs: add more parameter to the filesystem show Anand Jain
2013-10-15 17:22   ` David Sterba
2013-10-16  2:22     ` Anand Jain
2013-10-08  3:41 ` [PATCH 3/3] btrfs-progs: use BTRFS_SCAN_LBLKID as default scan in " Anand Jain
2013-10-15 17:13 ` [PATCH 1/3 v4] btrfs-progs: use kernel for mounted disk for show David Sterba
2013-10-16  9:25   ` Anand Jain
2013-10-16 13:09     ` David Sterba
2013-10-21 14:44   ` Josef Bacik
2013-10-22  5:53     ` Anand Jain
2013-10-22 13:21       ` Josef Bacik [this message]
2013-10-22 13:28         ` Hugo Mills
2013-10-22 16:52         ` David Sterba
2013-10-23 11:20           ` Anand Jain
2013-10-23 11:41             ` Anand Jain

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=20131022132147.GA27304@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=Anand.Jain@oracle.com \
    --cc=chris.mason@fusionio.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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).