public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Scrub errors but no errors ?!?
Date: Mon, 29 Jun 2015 10:25:31 +0000 (UTC)	[thread overview]
Message-ID: <pan$f19c8$49dbc00a$e7c9c955$478b9691@cox.net> (raw)
In-Reply-To: 3095967.p5MQJjsH62@zafu

Swâmi Petaramesh posted on Mon, 29 Jun 2015 10:42:14 +0200 as excerpted:

> Using kernel 3.19 on Ubuntu 15.04
> 
> I have a BTRFS Raid-1 FS made from 2 Luks-encrypted devices, each one
> built atop a bcache device.
> 
> The machine runs smoothly from this setup.
> 
> When I scrub said FS, it ends by spitting a message on console stating
> that "Scrub found errors but corrected them"
> 
> However if I then type :
> 
> # btrfs scrub stat /
> scrub status for 53a35066-1a7b-4fe1-9f94-a923a7f9e3af
>         scrub started at Sun Jun 28 11:17:50 2015 and finished after
>         30657 seconds
>         total bytes scrubbed: 3.01TiB with 0 errors


FWIW, I've seeing (and wondering) the same thing, tho with newer kernel 
(v4.1.0) and userspace (also v4.1)

I'm running pair-device raid1 mode (both data/metadata) but one of the 
two devices is slowly relocating sectors, so I thought it /might/ be 
btrfs detecting some oddness due to that.

But if you're seeing it too, that's unlikely.  So indeed, what's this 
found errors and corrected them bit, with no errors shown as found?

-- 
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-06-29 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29  8:42 Scrub errors but no errors ?!? Swâmi Petaramesh
2015-06-29 10:25 ` Duncan [this message]

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$f19c8$49dbc00a$e7c9c955$478b9691@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