From: Goffredo Baroncelli <kreijack@libero.it>
To: audio muze <audiomuze@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Using Btrfs on single drives
Date: Sat, 14 Nov 2015 12:09:21 +0100 [thread overview]
Message-ID: <56471661.6020101@libero.it> (raw)
In-Reply-To: <CA+LE0jwrdpjmJhwmG9Yv5HjqZh28-yp3Man8NSmXqCoB=JJ=Ew@mail.gmail.com>
On 2015-11-14 11:43, audio muze wrote:
> I can turn checksumming
> off given it's of no utility where a Btrfs volume is comprised of a
> single device only?
The checksums are used to detect a data corruption; in case of a btrfs-raid, the checksums are used *also* to pick the good copy.
BR
G.Baroncelli
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2015-11-14 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 10:43 Using Btrfs on single drives audio muze
2015-11-14 11:09 ` Goffredo Baroncelli [this message]
2015-11-14 16:35 ` Duncan
2015-11-15 3:27 ` audio muze
2015-11-15 4:01 ` Duncan
2015-11-15 6:30 ` Marc Joliet
2015-11-25 7:20 ` Russell Coker
2015-11-26 16:27 ` Duncan
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=56471661.6020101@libero.it \
--to=kreijack@libero.it \
--cc=audiomuze@gmail.com \
--cc=kreijack@inwind.it \
--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