public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Thomas Kupper <thomas@kupper.org>
Cc: Josef Bacik <josef@redhat.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: how to check data and metadata type
Date: Sat, 30 Jan 2010 13:20:01 -0500	[thread overview]
Message-ID: <20100130182000.GB7233@localhost.localdomain> (raw)
In-Reply-To: <E3FCE606-1BB2-4D76-8DB7-94B3534A8E7F@kupper.org>

On Sat, Jan 30, 2010 at 05:57:49PM +0100, Thomas Kupper wrote:
> 
> On 30 Jan 2010, at 16:18, Josef Bacik wrote:
> 
> > On Fri, Jan 29, 2010 at 11:43:45PM +0100, Thomas Kupper wrote:
> >> Just a short question:
> >> 
> >> How can I check the data and metadata modes of a multi-device btrfs device? btrfs-show is of no help and df is still not showing the correct size of it either (using latest btrfs kernel module and btrfs tools).
> > 
> > There are patches to do this for you, look for the "-i" patch for btrfs-progs
> > and the "df" patch for the kernel, that will give you the information you are
> > looking for.  Thanks,
> > 
> > Josef
> 
> Thanks Josef, I'm stuck with two problems : 
> 
> * found the df patch but it does not apply. The latest btrfs-unstable seems not have BTRFS_IOC_SNAP_LISTING, neither btrfs_ioctl_default_subvol. With what revision of btrfs do you work? Of course I could apply it manually but I'm interested in the snap listing, too :)
> 

Oh yeah sorry, there are other patches for snapshot listing and setting the
default snapshot/subvol to mount and my df patch was done on top of those other
patches.  If you just fix the rejections from my df patch it will work fine
since it doesn't depend on either of those patches.

Chris is going to make a "dangerous" branch on his btrfs-unstable git tree that
will have all of that work as well, so you should be able to use it shortly.

> * I did not succeed in finding the patch '-i'. If you would happen to know where I can find it? I was looking on linux-btrfs mailing list and asked the allknowing Google.
> 
> 

This is the btrfs-progs patch

http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg03808.html

and this is the kernel patch you'll want

http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg03807.html

Thanks,

Josef

  reply	other threads:[~2010-01-30 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29 22:43 how to check data and metadata type Thomas Kupper
2010-01-30 15:18 ` Josef Bacik
2010-01-30 16:57   ` Thomas Kupper
2010-01-30 18:20     ` Josef Bacik [this message]
2010-01-30 18:26       ` Thomas Kupper
2010-01-31  8:46       ` Thomas Kupper
2010-01-31  9:17         ` Thomas Kupper
2010-02-01 14:19           ` Josef Bacik
2010-02-03 15:21             ` Thomas Kupper
2010-01-31 17:39     ` Piavlo
2010-01-30 18:28       ` Thomas Kupper

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=20100130182000.GB7233@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=thomas@kupper.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