From: Harald Hoyer <harald@redhat.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC] A way to tell if all the devices in a file system are available
Date: Fri, 22 Jun 2012 12:33:59 +0200 [thread overview]
Message-ID: <4FE44A17.9070109@redhat.com> (raw)
In-Reply-To: <1340309431-9972-1-git-send-email-jbacik@fusionio.com>
On 06/21/2012 10:10 PM, Josef Bacik wrote:
> Harald Hoyer has had this as a feature request for ages and I've finally gotten
> around to hacking something up. This is probably going to get bikeshedded to
> death, bring it on, I'm not married to any of the behaviors in these patches, I
> just want to get the ball rolling so we can have something in place for 3.6.
>
> Basically all I've done is saved how many devices the super block thinks we have
> into the fs_devices struct whenever we scan a device. Then all we have to do
> for the IOCTL is compare how many devices the fs_devices struct has in it to how
> many we think we need.
>
> The command itself just spits out 0 for yay we're ready and 1 for boo no we're
> not. This makes it easier for Harald to do his multi-device btrfs support in
> dracut. Thanks,
>
> Josef
>
Exactly what I need! Thanks! Would be really usefu!
next prev parent reply other threads:[~2012-06-22 10:34 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
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 ` Harald Hoyer [this message]
2012-07-10 17:35 ` [RFC] A way to tell if all the devices in a file system are available 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=4FE44A17.9070109@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.