linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@inwind.it>
To: Josef Bacik <jbacik@fusionio.com>,
	linux-btrfs@vger.kernel.org, harald@redhat.com
Subject: Re: [PATCH] Btrfs: add DEVICE_READY ioctl
Date: Tue, 17 Jul 2012 19:17:43 +0200	[thread overview]
Message-ID: <50059E37.1020703@inwind.it> (raw)
In-Reply-To: <20120717115334.GA11226@twin.jikos.cz>

On 07/17/2012 01:53 PM, David Sterba wrote:
> On Fri, Jun 22, 2012 at 08:12:52PM +0200, Goffredo Baroncelli wrote:
>> On 06/21/2012 10:10 PM, Josef Bacik wrote:
>>> This will be used in conjunction with btrfs device ready <dev>.  This is
[....]
> 
>> Finally I am starting to think that we should definitely switch to a
>> /sys/btrfs style of interface
> 
> I'm all for a sysfs interface, having an ioctl way of retrieving
> information is good, but not practical for use from scripting languages,
> namely for writing tests.

Moreover a sysfs interface is more extensible for further enanchement

> 
> There are some guys working on the sysfs patches, I did preliminary
> reviews. The first step is to bring back the core sysfs support (mostly
> done iirc) and then exporting various information.
> I'll check what's the status.

Great, are there public patches, I am interested in contributing

> 
>> think something like:
>>
>> /sys/btrfs/<fs-uuid>/<dev-uuid>/present
>>                                size
>>                                space-occuped
>>                                number-of-error
>>                                [...]
>>
>> /sys/btrfs/<fs-uuid>/<subvolume-id>/read-only
>>                                     compressed
>>                                     raid-mode
>>                                     path
>>                                     [...]
>>
>> /sys/btrfs/<fs-uuid>/label
>>                      mounted
>>                      read-only
>>                      compressed
>>                      raid-mode
>>                      [...]
> 
> That's a good start for a discussion.
> 
> 
> david
> .
> 


  reply	other threads:[~2012-07-17 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 20:10 [RFC] A way to tell if all the devices in a file system are available Josef Bacik
2012-06-21 20:10 ` [PATCH] Btrfs: add DEVICE_READY ioctl Josef Bacik
2012-06-22 18:12   ` Goffredo Baroncelli
2012-07-17 11:53     ` David Sterba
2012-07-17 17:17       ` Goffredo Baroncelli [this message]
2012-06-21 20:10 ` [PATCH] Btrfs-progs: add btrfs device ready command Josef Bacik
2012-06-22 17:20   ` Goffredo Baroncelli
2012-06-22 10:33 ` [RFC] A way to tell if all the devices in a file system are available Harald Hoyer
2012-07-10 17:35 ` Harald Hoyer

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=50059E37.1020703@inwind.it \
    --to=kreijack@inwind.it \
    --cc=harald@redhat.com \
    --cc=jbacik@fusionio.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).