All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: <kreijack@inwind.it>, Lennart Poettering <lennart@poettering.net>,
	<linux-btrfs@vger.kernel.org>
Subject: Re: price to pay for nocow file bit?
Date: Wed, 7 Jan 2015 17:06:32 -0500	[thread overview]
Message-ID: <54ADADE8.4080507@fb.com> (raw)
In-Reply-To: <54AD9F85.1010608@inwind.it>

On 01/07/2015 04:05 PM, Goffredo Baroncelli wrote:
>>
>>> I am trying to understand the pros and cons of turning this bit
>>> on, before I can make this change. So far I see one big pro, but I
>>> wonder if there's any major con I should think about?
>>>
>>
>> Nope there's no real con other than you don't get csums, but that
>> doesn't really matter for you.  Thanks,
>
> In a btrfs-raid setup, in case of a corrupted sector, is BTRFS able to
> rebuild the sector ?
> I suppose no; if so this has to be add to the cons I think.
>

It won't know its corrupted, but it can rebuild if say you yank a drive 
and add a new one.  RAID5/RAID6 would catch corruption of course.  Thanks,

Josef

  reply	other threads:[~2015-01-07 22:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 17:43 price to pay for nocow file bit? Lennart Poettering
2015-01-07 20:10 ` Josef Bacik
2015-01-07 21:05   ` Goffredo Baroncelli
2015-01-07 22:06     ` Josef Bacik [this message]
2015-01-08  6:30   ` Duncan
2015-01-10 12:00     ` Martin Steigerwald
2015-01-10 12:23       ` Martin Steigerwald
2015-01-08  8:24   ` Chris Murphy
2015-01-08  8:35     ` Koen Kooi
2015-01-08 13:30   ` Lennart Poettering
2015-01-08 18:24     ` Konstantinos Skarlatos
2015-01-08 18:48       ` Goffredo Baroncelli
2015-01-09 15:52     ` David Sterba
2015-01-10 10:30       ` Martin Steigerwald
2015-01-11 20:39     ` Chris Murphy
2015-01-08 15:56 ` Zygo Blaxell
2015-01-08 16:53   ` Lennart Poettering
2015-01-08 18:36     ` Zygo Blaxell
2015-01-09 15:41       ` David Sterba
2015-01-09 16:14         ` Zygo Blaxell
2015-01-08 20:42     ` Roger Binns
2015-01-15 19:06     ` Chris Mason

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=54ADADE8.4080507@fb.com \
    --to=jbacik@fb.com \
    --cc=kreijack@inwind.it \
    --cc=lennart@poettering.net \
    --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.