linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian <cdysthe@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Mysterious device (id 0).
Date: Fri, 15 May 2015 11:36:10 -0400	[thread overview]
Message-ID: <mj53pb$qlu$1@ger.gmane.org> (raw)
In-Reply-To: <5555D78D.5040909@gmail.com>

On 05/15/2015 07:25 AM, Austin S Hemmelgarn wrote:

> 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.
>
>
No, I have never run 'btrfs replace'. This problem was discussed in a 
previous thread covering the script I am using for daily scrub. The 
author had the same problem, but for him it simply went away. Not for me 
though. The thread was

"Re: 3.19.3: check tree block failed + WARNING: device 0 not present on 
scrub".

I have had some problems with btrfs in the past so I am very ware of any 
error message! I can't live without the snapshots anymore though :)


-- 
//Christian



  reply	other threads:[~2015-05-15 15:36 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
2015-05-15 15:36   ` Christian [this message]
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='mj53pb$qlu$1@ger.gmane.org' \
    --to=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 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).