From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS, encrypted LVM and disk write cache ?
Date: Fri, 13 May 2011 10:59:53 +0200 [thread overview]
Message-ID: <1305277193.3052.24.camel@tethys> (raw)
In-Reply-To: <BANLkTimQVkzzhaQiur92KxQ2yBgGap5eRA@mail.gmail.com>
Hi Fajar,
Le vendredi 13 mai 2011 =C3=A0 13:54 +0700, Fajar A. Nugraha a =C3=A9cr=
it :
> Well, first of all, btrfs is still under heavy development.
The wiki https://btrfs.wiki.kernel.org/index.php/Main_Page says in bold=
:
=C2=AB Btrfs is under heavy development, but every effort is being made=
to
keep the filesystem stable and fast. As of 2.6.31, we only plan to make
forward compatible disk format changes, and many users have been
experimenting with Btrfs on their systems with good results. =C2=BB
Adding to the fact that it comes included with the stock and distro
kernels... That gives a bit contradictory signals... "Should I stay or
should I go ?"
Looks a bit like legal babble boiling down to =C2=AB Yes, it is suppose=
d to
work and be usable, so please use it, just be so kind no to sue us if
you run into trouble. Not our fault, we won't accept any liability. =C2=
=BB
> 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
Every distro has bugs. However Natty's kernel never ever hanged my
system until I shifted to using BTRFS... I won't relate BTRFS issues to
using Natty unless there is some evidence pointing in this direction...
Not wanting to troll, of course, uh... ;-)
> If you're used to ext4 speed, then you'll notice that btrfs is consid=
erably
> slower. That's why I use SSD to add some I/O speed (currently booting=
to gnome
> classic desktop only takes about 30 seconds).
Well, I noticed it's slower, still usable for me anyway, I'm a patient
guy ;-) Anyway an SSD is not an option to me, financially speaking ;-)
Kind regards.
--
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 8:59 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
2011-05-13 8:59 ` Swâmi Petaramesh [this message]
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=1305277193.3052.24.camel@tethys \
--to=swami@petaramesh.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
/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).