linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: kreijack@inwind.it
Cc: Goffredo Baroncelli <kreijack@libero.it>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH not for integration] btrfs-devlist: dumps btrfs_device and btrfs_fs_devices from kernel
Date: Wed, 30 Jul 2014 12:01:19 +0800	[thread overview]
Message-ID: <53D86E0F.7080703@oracle.com> (raw)
In-Reply-To: <53D35341.4080502@libero.it>




On 26/07/2014 15:05, Goffredo Baroncelli wrote:
> On 07/25/2014 02:33 PM, Anand Jain wrote:
>> This would dump the following info:
>>
>> fs_address dev_address dev_root_addr root_fsid
>> fsid name uuid (seed_fsid@seed_addr sprout_fsid@sprout_addr)
>> 	(fs_num_devices fs_open_devices fs_rw_devices fs_missing_devices fs_total_devices) fs_total_rw_bytes fs_num_can_discard
>> 	devid gen total_bytes disk_total_bytes bytes_used type io_align io_width sector_size fmode
>> 	not_fs_Mounted|not_fs_Seeding|not_fs_Rotating
>> 	not_Writable|not_MD|not_Missing|not_Discard|not_Replace_tgt|not_Run_pending|not_Nobarriers|not_Stat_valid|not_Bdev
>>
>> Applies on Chris integration branch now
>
> Hi Anand,
>
> why not export these information via sysfs ?


Thanks for the comments.

  If its for the purpose of recreating the kernel
  LIST_HEAD(fs_uuids) in the user-space, what would you
  choose ? sysfs / ioctl / memory-dump / any-other better way ?

Regds, Anand



> BR
> G.Baroncelli
>
>>
>> Anand Jain (1):
>>    btrfs: introduce BTRFS_IOC_GET_DEVS
>>
>>   fs/btrfs/super.c           |  86 +++++++++++++++++++++++++++
>>   fs/btrfs/volumes.c         | 145 +++++++++++++++++++++++++++++++++++++++++++++
>>   fs/btrfs/volumes.h         |   3 +
>>   include/uapi/linux/btrfs.h |  53 ++++++++++++++++-
>>   4 files changed, 286 insertions(+), 1 deletion(-)
>>
>> Anand Jain (1):
>>    btrfs-progs: introduce btrfs-devlist
>>
>>   .gitignore      |   1 +
>>   Makefile        |   4 +-
>>   btrfs-devlist.c | 268 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>   ioctl.h         |  52 +++++++++++
>>   4 files changed, 323 insertions(+), 2 deletions(-)
>>   create mode 100644 btrfs-devlist.c
>>
>
>

      reply	other threads:[~2014-07-30  4:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 12:33 [PATCH not for integration] btrfs-devlist: dumps btrfs_device and btrfs_fs_devices from kernel Anand Jain
2014-07-25 12:33 ` [PATCH 1/1] btrfs: introduce BTRFS_IOC_GET_DEVS Anand Jain
2014-07-25 12:33 ` [PATCH 1/1] btrfs-progs: introduce btrfs-devlist Anand Jain
2014-07-26  7:05 ` [PATCH not for integration] btrfs-devlist: dumps btrfs_device and btrfs_fs_devices from kernel Goffredo Baroncelli
2014-07-30  4:01   ` Anand Jain [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=53D86E0F.7080703@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=kreijack@inwind.it \
    --cc=kreijack@libero.it \
    --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).