linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 16:16:56 +0700	[thread overview]
Message-ID: <BANLkTi=CF--tqdo0AtnFYbaepMP=-_ZKuw@mail.gmail.com> (raw)
In-Reply-To: <1305277193.3052.24.camel@tethys>

On Fri, May 13, 2011 at 3:59 PM, Sw=E2mi Petaramesh <swami@petaramesh.o=
rg> wrote:
> Adding to the fact that it comes included with the stock and distro
> kernels... That gives a bit contradictory signals... "Should I stay o=
r
> should I go ?"
>
> Looks a bit like legal babble boiling down to =AB Yes, it is supposed=
 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. =BB

Something like that.
Note also since it's in heavy development, even a small difference in
kernel version can make a difference between whether a bug is present
or not, so it's advisable to always try latest kernel version.

>
>> 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.=
=2E.
>
> Not wanting to troll, of course, uh... ;-)

No troll taken.

Just wanted to point out that since Natty is new and has known bugs
(which might include kernel package as well), if you encounter
problems try to use latest available kernel for Natty first. If it
doesn't work, try latest vanilla kernel from kernel.org. For example,
IIRC 2.6.38 has a bug in that you can't use mount option "subvol=3D..."
if the fs/subvolume is newly created, while 2.6.39 works fine. At
least that's what I experienced, so now I use subvolid to select
subvolume.

>
>> If you're used to ext4 speed, then you'll notice that btrfs is consi=
derably
>> slower. That's why I use SSD to add some I/O speed (currently bootin=
g to gnome
>> classic desktop only takes about 30 seconds).
>
> Well, I noticed it's slower, still usable for me anyway, I'm a patien=
t
> guy ;-) Anyway an SSD is not an option to me, financially speaking ;-=
)

A 60GB Corsair Force should be about $140. Highly recommended. Higher
capacities provide even better cost/GB.

--=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

  reply	other threads:[~2011-05-13  9:16 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
2011-05-13  9:16         ` Fajar A. Nugraha [this message]
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='BANLkTi=CF--tqdo0AtnFYbaepMP=-_ZKuw@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).