All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: Anand Jain <Anand.Jain@oracle.com>
Cc: Mitch Harder <mitch.harder@sabayonlinux.org>,
	Berend Dekens <btrfs@cyberwizzard.nl>,
	Arne Jansen <sensille@gmx.net>,
	linux-btrfs@vger.kernel.org
Subject: Re: BTRFS and power loss ~= corruption?
Date: Thu, 25 Aug 2011 19:55:34 +0200	[thread overview]
Message-ID: <201108251955.35283.Martin@lichtvoll.de> (raw)
In-Reply-To: <4E55C217.4080203@oracle.com>

Am Donnerstag, 25. August 2011 schrieb Anand Jain:
>   anyways, solutions containing disk-write-cache disabled and SSD
>   is quite popular now a days. And in terms of random synchronous
>   write performance they are awesome.

There are SSD with capacitors such as Intel SSD 320. These according to=
=20
the vendor should write out all remaining writes that made it to the di=
sk=20
cache should a power loss occur.

I did not have any issues with BTRFS on / with a ThinkPad T520 and an=20
Intel SSD 320. /home is still Ext4, as I want a fsck first. Thats with=20
Linux 3.0.0-2 amd64 debian package.

That said I also do not have any issues with BTRFS on a ThinkPad T23 fo=
r /=20
and /home. But then the machine has an hibernate-to-disk-and-resume upt=
ime=20
of almost 120 days, so it didn=B4t see a power loss for a long time. Th=
ats=20
still with 2.6.38.4.

--=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
--
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-08-25 17:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 13:11 BTRFS and power loss ~= corruption? Berend Dekens
2011-08-24 13:31 ` Arne Jansen
2011-08-24 15:01   ` Berend Dekens
2011-08-24 15:04     ` *** GMX Spamverdacht *** " Arne Jansen
2011-08-24 15:13       ` Berend Dekens
2011-08-24 17:06         ` Mitch Harder
2011-08-24 21:00           ` Ahmed Kamal
2011-08-25  3:31           ` Anand Jain
2011-08-25 17:55             ` Martin Steigerwald [this message]
2011-08-25 22:16               ` Maciej Marcin Piechotka
2011-11-09 20:15                 ` Martin Steigerwald
2011-08-25 23:01 ` Gregory Maxwell
2011-08-26  6:37   ` Arne Jansen
2011-08-26  7:48     ` Mike Fleetwood
2011-08-26  9:30       ` Arne Jansen
2011-11-09 17:33   ` Stefan Behrens

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=201108251955.35283.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=Anand.Jain@oracle.com \
    --cc=btrfs@cyberwizzard.nl \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mitch.harder@sabayonlinux.org \
    --cc=sensille@gmx.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 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.