linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [BUG?] btrfs scrub -d doesn't scan all devices
Date: Sun, 27 Dec 2015 07:22:59 +0000 (UTC)	[thread overview]
Message-ID: <pan$bcf44$1632328c$31564c06$c04774a8@cox.net> (raw)
In-Reply-To: 1451187536.6446.14.camel@scientia.net

Christoph Anton Mitterer posted on Sun, 27 Dec 2015 04:38:56 +0100 as
excerpted:

> I've just noted the following behaviour:
> 
> # btrfs scrub start -Bdr /
> scrub device /dev/sda2 (id 1) done
> 	scrub started at Sun Dec 27 01:59:05 2015
>	and finished after 00:04:04
> 	total bytes scrubbed: 29.39GiB with 0 errors
> scrub device /dev/sdb2 (id 2) done
> 	scrub started at Sun Dec 27 01:59:05 2015
>	and finished after 00:04:08
> 	total bytes scrubbed: 29.39GiB with 0 errors
> 
> => that works as expected
> 
> However:
> # btrfs scrub start -Bdr /dev/disk/by-label/system
> scrub device /dev/sdb2 (id 2) done
> 	scrub started at Sun Dec 27 01:53:18 2015
>	and finished after 00:04:01
> 	total bytes scrubbed: 29.37GiB with 0 errors

> => seems to scan only sdb2 (which is where /dev/disk/by-label/system
> points to) at least, no output is given for sda2


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.

(The manpage specifically says "all devices of the filesystem identified 
by <path>".  Emphasis on _ALL_DEVICES_ if given a normal path.)

* When you point scrub at a specific device, it scrubs that specific 
device.

(The manpage continues ... "or on a single <device>." Emphasis on 
_SINGLE_DEVICE_ if given a device node.)


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.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-12-27  7:23 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 [this message]
2015-12-28  1:21   ` Christoph Anton Mitterer
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='pan$bcf44$1632328c$31564c06$c04774a8@cox.net' \
    --to=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 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).