linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Goffredo Baroncelli <kreijack@libero.it>" <kreijack@libero.it>
To: <chris.mason@fusionio.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: R: Re: Subvolumes and /proc/self/mountinfo
Date: Wed, 20 Jun 2012 13:51:11 +0200 (CEST)	[thread overview]
Message-ID: <10842956.228491340193071904.JavaMail.defaultUser@defaultHost> (raw)

HI all,

>----Messaggio originale----
>Da: chris.mason@fusionio.com
>Data: 20/06/2012 1.49
>A: "H. Peter Anvin"<hpa@zytor.com>
>Cc: "linux-btrfs@vger.kernel.org"<linux-btrfs@vger.kernel.org>
>Ogg: Re: Subvolumes and /proc/self/mountinfo
>

>> b. Are there better ways (walking the tree using BTRFS_IOC_TREE_SEARCH?)
>> to accomplish this than using /proc/self/mountinfo?
>
>Not yet, but I'm definitely open to adding them.  Lets just hash out
>what you need and we'll either go through Kay's stuff or add ioctls for
>you.

Chris, what about adding a /sys/btrfs/<fs-uuid>/<subvol-id> interface ?

For example under

/sys/btrfs/<fs-uuid>

we can list the devices which btrfs uses

under 

/sys/btrfs/<fs-uuid>/<subvol-id> 

we can show/set the subvolume properties (like RO, compres....)

>
>-chris
>--
>To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



             reply	other threads:[~2012-06-20 11:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 11:51 Goffredo Baroncelli <kreijack@libero.it> [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-20 12:02 R: Re: Subvolumes and /proc/self/mountinfo Goffredo Baroncelli <kreijack@libero.it>
2012-06-20 15:37 ` H. Peter Anvin
2012-06-20 16:34   ` Goffredo Baroncelli
2012-06-20 17:41     ` H. Peter Anvin
2012-06-20 18:06       ` Goffredo Baroncelli
2012-06-20 19:15         ` Helmut Hullen
2012-06-20 20:22           ` Goffredo Baroncelli
2012-06-20 21:49         ` H. Peter Anvin
2012-06-21  5:47           ` Goffredo Baroncelli
2012-06-21 11:46             ` Martin Steigerwald
2012-06-21 17:05               ` Goffredo Baroncelli
2012-06-21 13:38             ` H. Peter Anvin
2012-06-21 17:05               ` Goffredo Baroncelli
2012-06-21 17:11                 ` H. Peter Anvin
2012-06-20 12:10 Goffredo Baroncelli <kreijack@libero.it>

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=10842956.228491340193071904.JavaMail.defaultUser@defaultHost \
    --to=kreijack@libero.it \
    --cc=chris.mason@fusionio.com \
    --cc=hpa@zytor.com \
    --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).