Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: scrub "correcting" tons of errors ?
Date: Fri, 29 Mar 2013 08:58:32 -0400	[thread overview]
Message-ID: <20130329125832.GB1876@localhost.localdomain> (raw)
In-Reply-To: <515563D7.3020706@petaramesh.org>

On Fri, Mar 29, 2013 at 03:50:15AM -0600, Swâmi Petaramesh wrote:
> Hi there,
> 
> I've started "btrfs scrub start /" on one of my machines (Kernel
> 3.8.0-15 Ubuntu AMD64), which typically "behaves well" so I wasn't
> suspected any disk issue.
> 
> After having ran for only 165 seconds, "scrub status" shows it pretends
> having found and corrected 22926 CSUM errors ??!?!?!?!!???
> 
> This is a rather new HDD, in perfect shape (SMART all OK, never
> reallocated a single sector, less than 200 hours total runtime...)
> 
> WTF ?!?
> 
> I've cancelled scrub for now, until I get further understanding of what
> can be happening...
> 

So this is probably because of the extent tree corruption you had, it's just
cleaning things up and you should be fine once it finishes.  Thanks,

Josef

  reply	other threads:[~2013-03-29 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29  9:50 scrub "correcting" tons of errors ? Swâmi Petaramesh
2013-03-29 12:58 ` Josef Bacik [this message]
2013-03-29 13:06   ` Swâmi Petaramesh
2013-03-29 13:12     ` Josef Bacik
2013-03-29 13:23       ` Swâmi Petaramesh
2013-03-29 13:35       ` Swâmi Petaramesh
2013-03-29 13:26     ` Josef Bacik
2013-03-29 13:29       ` cwillu
2013-03-29 13:39       ` Swâmi Petaramesh
2013-03-29 13:57         ` Josef Bacik
2013-03-29 13:06   ` Harald Glatt
2013-03-29 13:11     ` Hugo Mills

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=20130329125832.GB1876@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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