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:21:28 +0100	[thread overview]
Message-ID: <1451265688.6320.22.camel@scientia.net> (raw)
In-Reply-To: <pan$bcf44$1632328c$31564c06$c04774a8@cox.net>

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

On Sun, 2015-12-27 at 07:22 +0000, Duncan wrote:
> I'd call that NOTABUG.  As the btrfs-scrub manpage suggests:
> 
> * When you point scrub at a mountpoint, it scrubs all devices
> composing 
> that filesystem.
Uhm,.. mine doesn't contain this,... neither do those of the master or
devel branches from David's repo... or am I just blind?

Actually it says:
>DESCRIPTION
>       btrfs scrub is used to scrub a btrfs filesystem, which will read all
>       data from all disks and verify checksums.

Also, if it would allow to only selectively scrub parts of the fs (e.g.
just some devices or subpaths/subvols/files) than the whole syntax for
cancel, break, etc. would become ambiguous.

> Since /dev/disk/by-*/* are symlinks to various block-device nodes,
> it 
> follows that if you point scrub at them, only the device pointed at
> is 
> scrubbed, exactly as one might expect based on the manpage.
Sure... that was clear... but I have another manpage than yours...
perhaps some distro specific patch?

Chris.

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

  reply	other threads:[~2015-12-28  1:21 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 [this message]
2015-12-28  1:25     ` Christoph Anton Mitterer
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=1451265688.6320.22.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.