From: Hugo Mills <hugo@carfax.org.uk>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Subvolume level allocation policy
Date: Sun, 23 Oct 2011 19:52:38 +0100 [thread overview]
Message-ID: <20111023185238.GC29548@carfax.org.uk> (raw)
In-Reply-To: <4EA4620A.3060702@cfl.rr.com>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
On Sun, Oct 23, 2011 at 02:50:50PM -0400, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Is it ( yet? ) possible to manipulate the allocation policy on a
> subvolume level instead of the fs level? For example, to make / use
> raid1, and /home use raid0? Or to have / allocated from an ssd and
> /home allocated from the giant 2tb hd.
Not yet, sorry. It's planned, but nobody's got around to
implementing it.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- I'm on a 30-day diet. So far I've lost 18 days. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-10-23 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 18:50 Subvolume level allocation policy Phillip Susi
2011-10-23 18:52 ` Hugo Mills [this message]
2011-10-24 9:44 ` Jan Schmidt
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=20111023185238.GC29548@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=psusi@cfl.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox