From: Jim Salter <jim@jrs-s.net>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Scrubbing with BTRFS Raid 5
Date: Tue, 21 Jan 2014 13:25:46 -0500 [thread overview]
Message-ID: <52DEBBAA.4020200@jrs-s.net> (raw)
In-Reply-To: <D97DCF6D-6057-41FC-95B7-AC4127F51B16@colorremedies.com>
There are different values of "testing" and of "production" - in my
world, at least, they're not atomically defined categories. =)
On 01/21/2014 12:38 PM, Chris Murphy wrote:
> It's for testing purposes. If you really want to commit a production
> machine for testing a file system, and you're prepared to lose 100% of
> changes since the last backup, OK do that.
next prev parent reply other threads:[~2014-01-21 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 9:06 Scrubbing with BTRFS Raid 5 Graham Fleming
2014-01-21 17:08 ` Duncan
2014-01-21 17:18 ` Jim Salter
2014-01-21 17:38 ` Chris Murphy
2014-01-21 18:25 ` Jim Salter [this message]
2014-01-22 16:02 ` Duncan
2014-01-22 20:45 ` Chris Mason
2014-01-22 21:06 ` ronnie sahlberg
2014-01-22 21:16 ` Chris Mason
2014-01-22 22:36 ` ronnie sahlberg
-- strict thread matches above, loose matches on Subject: below --
2014-01-21 18:03 Graham Fleming
2014-01-22 15:39 ` Duncan
2014-01-20 0:53 Graham Fleming
2014-01-20 13:21 ` 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=52DEBBAA.4020200@jrs-s.net \
--to=jim@jrs-s.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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