From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs scrub failure for raid 6 kernel 4.3
Date: Mon, 28 Dec 2015 01:39:34 +0100 [thread overview]
Message-ID: <1451263174.6320.5.camel@scientia.net> (raw)
In-Reply-To: <CAJCQCtSHWTqn7zzCtUtGjpr5=dMqfC1aGWaeNpZyVVhjrCvDHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Sun, 2015-12-27 at 11:29 -0700, Chris Murphy wrote:
> then the scrub request is effectively a
> scrub for a volume with a missing drive which you probably wouldn't
> ever do, you'd first replace the missing device.
While that's probably the normal work flow,... it should still work the
other way round... and if not, I'd consider that a bug.
> but when the drive is
> reattached it is not automatically re-added.
Which is good, as it would allow for similar attacks as we've recently
discussed in the other thread...
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-12-28 0:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 13:59 Btrfs scrub failure for raid 6 kernel 4.3 Waxhead
2015-12-27 18:29 ` Chris Murphy
2015-12-27 23:06 ` Waxhead
2015-12-28 1:48 ` Duncan
2015-12-28 2:04 ` Waxhead
2015-12-28 2:18 ` Chris Murphy
2015-12-28 21:08 ` Waxhead
2015-12-28 21:23 ` Chris Murphy
[not found] ` <5681BDD0.1060407@online.no>
2015-12-29 0:29 ` Chris Murphy
2015-12-29 20:19 ` Waxhead
2015-12-30 4:22 ` Chris Murphy
2015-12-30 18:31 ` Waxhead
2015-12-30 19:08 ` Waxhead
2015-12-28 4:02 ` Duncan
2015-12-28 21:17 ` Waxhead
2015-12-28 21:50 ` Chris Murphy
2015-12-28 0:39 ` Christoph Anton Mitterer [this message]
2015-12-28 0:58 ` Chris Murphy
2015-12-28 1:09 ` Christoph Anton Mitterer
2015-12-28 1:23 ` Chris Murphy
2015-12-28 1:31 ` Christoph Anton Mitterer
2015-12-28 2:16 ` Duncan
2015-12-28 1: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=1451263174.6320.5.camel@scientia.net \
--to=calestyo@scientia.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 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).