From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Christian <cdysthe@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Mysterious device (id 0).
Date: Fri, 15 May 2015 07:25:01 -0400 [thread overview]
Message-ID: <5555D78D.5040909@gmail.com> (raw)
In-Reply-To: <mj3dg9$h3k$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
On 2015-05-14 20:09, Christian wrote:
> Hi,
>
> My laptop has a small ext4 /boot partition /dev/sda1 and a large btrfs
> partition containing / and /home as a sub volume /dev/sda3
>
> When I run scrub on /dev/sda3 and check status with sudo btrfs scrub
> status -d /dev/sda3 I get:
>
> scrub status for 3d52dc93-c89f-453f-965d-8601d11e7710
> scrub device /dev/sda3 (id 1) history
> scrub started at Thu May 14 19:54:02 2015 and finished after 235
> seconds
> total bytes scrubbed: 111.03GiB with 0 errors
> scrub device (id 0) history
> scrub started at Thu May 14 19:54:02 2015 and was aborted after 0
> seconds
> total bytes scrubbed: 0.00B with 0 errors
>
> As device (id 0) is indicated, but I have no idea what it is.
>
> When I run scrub with a script (cron) the same device (id 0) shows up in
> a warning:
>
> /etc/cron.daily/btrfs-scrub:
> WARNING: device 0 not present
> scrub device /dev/sda3 (id 1) done
> scrub started at Sat May 2 08:03:46 2015 and finished after 241
> seconds
> total bytes scrubbed: 109.06GiB with 0 errors
> scrub device (id 0) canceled
> scrub started at Sat May 2 08:03:46 2015 and was aborted after 0
> seconds
> total bytes scrubbed: 0.00B with 0 errors
>
> What is this device (id 0) which never gets scrubbed but always shows up?
>
> I'm running Ubuntu 15.04 with the 3.19.0-16-generic kernel.
>
Have you ever run 'btrfs replace' to replace a device in the filesystem?
I know that new device in a replace operation get's tagged as device
id 0 until the replace operation completes (at which point it gets the
devid of the device it replaced). Personally, this is the only case
that I know of that devid 0 is actually used in the code. Thinking
further though, it might also be an off-by-one error somewhere, although
I have no idea where.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2015-05-15 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 0:09 Mysterious device (id 0) Christian
2015-05-15 11:25 ` Austin S Hemmelgarn [this message]
2015-05-15 15:36 ` Christian
2015-05-15 16:20 ` Anand Jain
2015-05-15 16:37 ` Christian
2015-05-15 16:51 ` Anand Jain
2015-05-15 17:17 ` Christian
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=5555D78D.5040909@gmail.com \
--to=ahferroin7@gmail.com \
--cc=cdysthe@gmail.com \
--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.