From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: scrub "correcting" tons of errors ?
Date: Fri, 29 Mar 2013 14:06:33 +0100 [thread overview]
Message-ID: <515591D9.5010802@petaramesh.org> (raw)
In-Reply-To: <20130329125832.GB1876@localhost.localdomain>
Hi Josef,
Le 29/03/2013 13:58, Josef Bacik a écrit :
> 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,
Er... It's on a different machine !
Current (at the time I write) status is :
# btrfs scrub status /
scrub status for 346b81b2-0735-4c4d-a137-1995bc78ad70
scrub resumed at Fri Mar 29 11:52:43 2013 and finished after
7470 seconds
total bytes scrubbed: 231.96GB with 149691 errors
error details: csum=149691
corrected errors: 149691, uncorrectable errors: 0, unverified
errors: 0
I have to say that scrub completely froze the machine at least 4 times
(disk had ceased activity and any command that would imply a disk access
would hang forever), but at least after a (quite brutal) reboot it could
be resumed...
The only thing about this FS is that it had been imaged, then restored,
using partclone.btrfs (which itself is supposed to use the BTRFS libraries).
I have a screenshot of "last thing I saw when it hanged", I can upload
it somewhere, should it be relevant...
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.
next prev parent reply other threads:[~2013-03-29 13:06 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
2013-03-29 13:06 ` Swâmi Petaramesh [this message]
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=515591D9.5010802@petaramesh.org \
--to=swami@petaramesh.org \
--cc=jbacik@fusionio.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.