All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Linux BTRFS <linux-btrfs@vger.kernel.org>
Subject: BTRFS, encrypted LVM and disk write cache ?
Date: Thu, 12 May 2011 07:45:25 +0200	[thread overview]
Message-ID: <1305179125.3106.3.camel@tethys> (raw)

Hi list,

I'm a new BTRFS user and will try not to ask FAQs ;-)

I'm currently using Btrfs v0.19 on stock Ubuntu Natty (kernel 2.6.38)
and use a BTRFS inside an encrypted LVM.

The wiki "gotchas" page https://btrfs.wiki.kernel.org/index.php/Gotchas
states :
=C2=AB btrfs volumes on top of dm-crypt block devices (and possibly LVM=
)
require write-caching to be turned off on the underlying HDD. Failing t=
o
do so, in the event of a power failure, may result in corruption not ye=
t
handled by btrfs code. (2.6.33) =C2=BB

=2E..So I've turned my write cache off, but I notice this is stated for
kernel 2.6.33, so wonder if this still is an issue with 2.6.38, or has
it been addressed since ?

Thanks in advance for your help.

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

             reply	other threads:[~2011-05-12  5:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  5:45 Swâmi Petaramesh [this message]
2011-05-12 15:42 ` BTRFS, encrypted LVM and disk write cache ? 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
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=1305179125.3106.3.camel@tethys \
    --to=swami@petaramesh.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.