From: Fahrzin Hemmati <fahhem2@gmail.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: filesystem full when it's not? out of inodes? huh?
Date: Sat, 25 Feb 2012 18:37:24 -0800 [thread overview]
Message-ID: <4F499AE4.80908@gmail.com> (raw)
In-Reply-To: <jic4m8$j6g$1@dough.gmane.org>
On 2/25/2012 6:16 PM, Brian J. Murrell wrote:
>> Others might know of a way of changing the allocation size to less than
>> 1GB, but otherwise I recommend switching to something more stable like
>> ext4/reiserfs/etc.
> So btrfs is still not yet suitable to be a root/usr/var filesystem, even
> in kernel 3.0.0?
>
> b.
>
Nope, still in heavy development, though you should upgrade to 3.2.
Also, the devs mentioned in several places it's not friendly to small
drives, and I'm pretty sure 5GB is considered tiny.
I don't think you need to separate /usr out to it's own disk. You could
instead create a single drive with multiple subvolumes for /, /var,
/usr, etc. When you have Ubuntu use btrfs for /, it creates @ and @home
for / and /home, respectively, so it's a common phenomenon if you look
for help.
--Farz
next prev parent reply other threads:[~2012-02-26 2:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 1:55 filesystem full when it's not? out of inodes? huh? Brian J. Murrell
2012-02-26 2:10 ` Fahrzin Hemmati
2012-02-26 2:16 ` Brian J. Murrell
2012-02-26 2:37 ` Fahrzin Hemmati [this message]
2012-02-26 3:57 ` Brian J. Murrell
2012-02-26 4:05 ` Fahrzin Hemmati
2012-03-09 22:02 ` Johannes Hirte
2012-02-26 8:52 ` Duncan
2012-02-26 9:10 ` Helmut Hullen
2012-02-26 9:41 ` Duncan
2012-03-03 10:25 ` Chris Samuel
2012-02-26 5:45 ` Brian J. Murrell
2012-02-26 5:50 ` Fahrzin Hemmati
2012-02-26 6:14 ` Brian J. Murrell
2012-02-26 7:19 ` Jérôme Poulin
2012-02-26 19:43 ` Brian J. Murrell
2012-02-26 11:00 ` Hugo Mills
2012-03-02 11:50 ` Brian J. Murrell
2012-03-02 12:23 ` Fajar A. Nugraha
2012-02-26 19:37 ` Daniel Lee
2012-02-26 19:48 ` Brian J. Murrell
2012-02-26 19:52 ` Daniel Lee
2012-02-26 20:05 ` Brian J. Murrell
2012-02-26 20:25 ` Daniel Lee
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=4F499AE4.80908@gmail.com \
--to=fahhem2@gmail.com \
--cc=brian@interlinx.bc.ca \
--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).