linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Josef Bacik <josef@redhat.com>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS, encrypted LVM and disk write cache ?
Date: Thu, 12 May 2011 23:36:44 +0200	[thread overview]
Message-ID: <1305236204.3277.1.camel@tethys> (raw)
In-Reply-To: <20110512154224.GD19041@dhcp231-156.rdu.redhat.com>

Hi,

Le jeudi 12 mai 2011 =C3=A0 11:42 -0400, Josef Bacik a =C3=A9crit :
> >=20
> > ...So I've turned my write cache off, but I notice this is stated f=
or
> > kernel 2.6.33, so wonder if this still is an issue with 2.6.38, or =
has
> > it been addressed since ?

> If you mount and start writing and don't see a message in dmesg about=
 disabling
> barriers then you should be good to go.  Thanks,

I've turned disk cache back on and don't see no such messages in my
logs... So I assume I should be safe ?

However shifting from ext3 to BTRFS has been enough to turn my perfectl=
y
stable system into a perfectly unstable and crash-prone system :-/

--
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 21:36 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 [this message]
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=1305236204.3277.1.camel@tethys \
    --to=swami@petaramesh.org \
    --cc=josef@redhat.com \
    --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).