From: Pete <pete@petezilla.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Error on rebooting
Date: Fri, 26 Jul 2013 13:10:02 +0100 [thread overview]
Message-ID: <51F2671A.6080705@petezilla.co.uk> (raw)
In-Reply-To: <20130726074752.GK20517@carfax.org.uk>
Hugo,
thanks.
On 07/26/2013 08:47 AM, Hugo Mills wrote:
> Looks like it. I'd recommend a scrub to check for any other out of
> date data on the affected drive. I've done pretty much the same thing
> as this myself, and a scrub, though scary in the amount of noise it
> made, fixed everything satisfactorily.
bash-4.2# btrfs scrub start -Bd /mnt/data-pool/
scrub device /dev/sdb (id 1) done
scrub started at Fri Jul 26 08:18:00 2013 and finished after
9849 seconds
total bytes scrubbed: 984.77GB with 540 errors
error details: verify=20 csum=520
corrected errors: 540, uncorrectable errors: 0, unverified
errors: 0
So a bit of a wobble but raid1 to the rescue! Not sure what caused the
wobble. But all is well now.
Pete
prev parent reply other threads:[~2013-07-26 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 0:19 Error on rebooting Pete
2013-07-26 7:47 ` Hugo Mills
2013-07-26 12:10 ` Pete [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=51F2671A.6080705@petezilla.co.uk \
--to=pete@petezilla.co.uk \
--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).