From: Andi Kleen <andi@firstfloor.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Ric Wheeler <rwheeler@redhat.com>,
Lennart Poettering <lennart@poettering.net>,
Josef Bacik <josef@redhat.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: add a disk info ioctl to get the disks attached to a filesystem
Date: Thu, 30 Sep 2010 15:47:37 +0200 [thread overview]
Message-ID: <87tyl7uyva.fsf@basil.nowhere.org> (raw)
In-Reply-To: <AANLkTi=tzfR2RQzXP6MbzzZmxdpqPO=WQPFs4QSGseHi@mail.gmail.com> (Kay Sievers's message of "Thu, 30 Sep 2010 09:43:00 +0200")
Kay Sievers <kay.sievers@vrfy.org> writes:
>
> Yeah, we thought about that too, but a btrfs mount does not show up as
> a block device, like md/dm, so there is no place for a slaves/
> directory in /sys with the individual disks listed. How could be solve
> that? Create some fake blockdev for every btrfs mount, but that can't
> be used to read/write raw blocks?
You could simply create a new class for btrfs? (or maybe a generic
"compound" class)
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-09-30 13:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 20:53 [PATCH] Btrfs: add a disk info ioctl to get the disks attached to a filesystem Josef Bacik
2010-09-28 22:28 ` Goffredo Baroncelli
2010-09-29 0:24 ` Josef Bacik
2010-09-28 23:25 ` Christoph Hellwig
2010-09-29 0:08 ` Josef Bacik
2010-09-29 0:19 ` Lennart Poettering
2010-09-29 7:25 ` Ric Wheeler
2010-09-29 8:04 ` Kay Sievers
2010-09-29 23:43 ` Christoph Hellwig
2010-09-30 0:32 ` Josef Bacik
2010-09-30 7:43 ` Kay Sievers
2010-09-30 12:38 ` Josef Bacik
2010-09-30 13:47 ` Andi Kleen [this message]
2010-09-30 19:48 ` Josef Bacik
2010-09-30 19:59 ` Kay Sievers
2010-09-30 20:37 ` Lennart Poettering
2010-09-29 11:59 ` Lennart Poettering
2010-09-29 12:08 ` Ric Wheeler
2010-09-29 12:19 ` Kay Sievers
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=87tyl7uyva.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=hch@infradead.org \
--cc=josef@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=lennart@poettering.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=rwheeler@redhat.com \
/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.