All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gian-Carlo Pascutto <gcp@sjeng.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: The FAQ on fsync/O_SYNC
Date: Mon, 20 Apr 2015 10:13:47 +0200	[thread overview]
Message-ID: <mh2cfv$7rr$1@ger.gmane.org> (raw)
In-Reply-To: <20150420042731.GA20194@hungrycats.org>

On 20-04-15 06:27, Zygo Blaxell wrote:

>> I'm curious as to whether +C has any effect on BTRFS's durability, too.
> 
> I would expect it to be strictly equal to or worse than the CoW
> durability.

In addition to the stuff pointed out, I've wondered about this:
PostgreSQL full_page_writes copies 8k pages in order to prevent
corruption from partial writes. But btrfs has 16k pages by default, so a
corrupted FS page would corrupt more data than PostgreSQL protects.

Maybe it's not an issue if the underlying HW has 512b/4k sectors, or
maybe I'm misunderstanding what the respective features assume, but
unless informed to the contrary I wouldn't be entirely comfortable with
this.

(With CoW enabled, you don't have partial writes, so the point is moot)

-- 
GCP


  parent reply	other threads:[~2015-04-20  8:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19 13:20 The FAQ on fsync/O_SYNC Craig Ringer
2015-04-19 14:28 ` Martin Steigerwald
2015-04-19 14:31   ` Craig Ringer
2015-04-19 15:10     ` Martin Steigerwald
2015-04-19 15:18       ` Hugo Mills
2015-04-19 17:50         ` Martin Steigerwald
2015-04-19 18:18           ` Hugo Mills
2015-04-19 18:41             ` Martin Steigerwald
2015-04-19 18:51               ` Hugo Mills
2015-04-19 15:28     ` Russell Coker
2015-04-20  4:27     ` Zygo Blaxell
2015-04-20  6:07       ` Duncan
2015-04-21  1:31         ` Zygo Blaxell
2015-04-20  8:13       ` Gian-Carlo Pascutto [this message]
2015-04-20 15:19         ` Zygo Blaxell
2015-04-21 19:07       ` Chris Murphy
2015-04-20  3:29 ` Craig Ringer

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='mh2cfv$7rr$1@ger.gmane.org' \
    --to=gcp@sjeng.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.