From: "Fajar A. Nugraha" <list@fajar.net>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS, encrypted LVM and disk write cache ?
Date: Fri, 13 May 2011 13:54:44 +0700 [thread overview]
Message-ID: <BANLkTimQVkzzhaQiur92KxQ2yBgGap5eRA@mail.gmail.com> (raw)
In-Reply-To: <1305236204.3277.1.camel@tethys>
On Fri, May 13, 2011 at 4:36 AM, Sw=E2mi Petaramesh <swami@petaramesh.o=
rg> wrote:
> However shifting from ext3 to BTRFS has been enough to turn my perfec=
tly
> stable system into a perfectly unstable and crash-prone system :-/
Well, first of all, btrfs is still under heavy development. Add to
that the fact that you use Ubuntu Natty, which also have some known
bugs. There should be some hints there on what the outcome would be :P
Anyway, I'm using linux-image-2.6.38-9-generic from natty-proposed,
with btrfs as "/", separate /boot/grub on ext4, and Corsair Force SSD.
It works great so far. If you're used to ext4 speed, then you'll
notice that btrfs is considerably slower. That's why I use SSD to add
some I/O speed (currently booting to gnome classic desktop only takes
about 30 seconds).
So in summary, if you have problems but still want to try btrfs, try
upgrading your kernel. If you think it's too slow to be usable, then
the best you can try right now is use SSD.
--=20
=46ajar
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-13 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 5:45 BTRFS, encrypted LVM and disk write cache ? Swâmi Petaramesh
2011-05-12 15:42 ` Josef Bacik
2011-05-12 21:36 ` Swâmi Petaramesh
2011-05-13 6:54 ` Fajar A. Nugraha [this message]
2011-05-13 8:59 ` Swâmi Petaramesh
2011-05-13 9:16 ` Fajar A. Nugraha
2011-05-13 9:33 ` Swâmi Petaramesh
2011-05-13 9:43 ` Fajar A. Nugraha
2011-05-13 11:13 ` Swâmi Petaramesh
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=BANLkTimQVkzzhaQiur92KxQ2yBgGap5eRA@mail.gmail.com \
--to=list@fajar.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=swami@petaramesh.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).