All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: [BUG?] btrfs scrub -d doesn't scan all devices
Date: Mon, 28 Dec 2015 02:25:37 +0100	[thread overview]
Message-ID: <1451265937.6320.26.camel@scientia.net> (raw)
In-Reply-To: <1451265688.6320.22.camel@scientia.net>

[-- Attachment #1: Type: text/plain, Size: 709 bytes --]

Hey.

Just noted, mine says this:
>Start a scrub on all devices of the filesystem identified by <path>
>or on a single <device>. If a scrub is already running, the new one
>fails.
still not the text you quoted,... but there it is.

Anyway... it still contradicts the main description which implies that
a scrub always scrubs everything,... so I'd still call that a
documentation bug.


Further,...
- Eithr btrfs start allows multiple devices to be specified (which
  isn't documented either,
- or it should allow that.
- or using -d makes no sense when the scrub is launched on a device
  (instead of a mount point) and should thus fail or give at least a
  warning.


Cheers,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]

  reply	other threads:[~2015-12-28  1:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-27  3:38 [BUG?] btrfs scrub -d doesn't scan all devices Christoph Anton Mitterer
2015-12-27  7:22 ` Duncan
2015-12-28  1:21   ` Christoph Anton Mitterer
2015-12-28  1:25     ` Christoph Anton Mitterer [this message]
2015-12-28  1:36       ` Chris Murphy
2015-12-28  3:30       ` Duncan
2015-12-28  4:37         ` Christoph Anton Mitterer
2015-12-28  1:27     ` Chris Murphy
2015-12-28  3:16     ` 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=1451265937.6320.26.camel@scientia.net \
    --to=calestyo@scientia.net \
    --cc=1i5t5.duncan@cox.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.