From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: "cheater00 ." <cheater00@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Bad fs performance, IO freezes
Date: Tue, 27 Oct 2015 16:22:13 +0100 [thread overview]
Message-ID: <562F96A5.5080509@googlemail.com> (raw)
In-Reply-To: <CA+9GZUhfnuuCgf+kgR8a6MH+k1gih4U-O+mZaZmY6ETNZJvDKQ@mail.gmail.com>
On 10/27/15 16:07, cheater00 . wrote:
> Can I have nodatacow but still have checksumming?
No, see "nodatacow":
https://btrfs.wiki.kernel.org/index.php/Mount_options
Torrents are typically rehashed both on a per-block basis and after
completion. That won't protect you from bitflips or fs corruption, but
then again you don't have data redundancy anyway, so it doesn't really
matter.
Also any silently bitflipped blocks will be rejected by peers since
they don't match they block hash, so even in that case you won't be
distributing corrupt data.
-h
next prev parent reply other threads:[~2015-10-27 15:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 12:16 Bad fs performance, IO freezes cheater00 .
2015-10-26 13:32 ` Donald Pearson
2015-10-26 13:36 ` cheater00 .
2015-10-26 13:45 ` Donald Pearson
2015-10-26 13:46 ` cheater00 .
2015-10-26 13:56 ` cheater00 .
2015-10-26 14:00 ` Donald Pearson
2015-10-26 14:25 ` Liu Bo
2015-10-26 14:38 ` cheater00 .
2015-10-26 15:40 ` cheater00 .
2015-10-26 17:43 ` cheater00 .
2015-10-26 18:31 ` cheater00 .
2015-10-27 2:00 ` cheater00 .
2015-10-27 6:39 ` Duncan
2015-10-27 8:55 ` cheater00 .
2015-10-27 11:44 ` Austin S Hemmelgarn
2015-10-27 13:00 ` Henk Slager
2015-10-27 13:30 ` Austin S Hemmelgarn
2015-10-27 14:22 ` cheater00 .
2015-10-27 14:26 ` cheater00 .
2015-10-27 14:30 ` cheater00 .
2015-10-27 14:43 ` cheater00 .
2015-10-27 15:01 ` Holger Hoffstätte
2015-10-27 15:05 ` cheater00 .
2015-10-27 15:07 ` cheater00 .
2015-10-27 15:22 ` Holger Hoffstätte [this message]
2015-10-27 15:26 ` Austin S Hemmelgarn
2015-10-29 13:03 ` cheater00 .
2015-10-29 14:00 ` Austin S Hemmelgarn
2015-10-29 15:49 ` cheater00 .
2015-10-29 18:49 ` Henk Slager
2015-10-29 20:01 ` Austin S Hemmelgarn
2015-11-06 13:37 ` cheater00 .
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=562F96A5.5080509@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=cheater00@gmail.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).