From: Hugo Mills <hugo@carfax.org.uk>
To: Andy Smith <andy@strugglers.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Is this normal? Should I use scrub?
Date: Wed, 1 Apr 2015 15:42:02 +0000 [thread overview]
Message-ID: <20150401154202.GD32078@carfax.org.uk> (raw)
In-Reply-To: <20150401151114.GR4327@bitfolk.com>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
Hi, Andy,
On Wed, Apr 01, 2015 at 03:11:14PM +0000, Andy Smith wrote:
> I have a 6 device RAID-1 filesystem:
[snip tale of a filesystem with out of data data on one copy of the RAID]
> I have now got a new enclosure and put this system back together
> with all six devices. I was not expecting this filesystem to mount
> without assistance on boot because of /dev/sdk being "stale"
> compared to the other devices. I suppose this incorrect view is a
> holdover from my experience with mdadm.
>
> Anyway, I booted it and /srv/tank was mounted automatically with all
> six devices. I got a bunch of these messages as soon as it was
> mounted:
>
> http://pastie.org/private/2ghahjwtzlcm6hwp66hkg
>
> There's lots more of it but it's all like that. That paste is from
> the end of the log and there haven't been any more such message
> since, so that's about 20 minutes (the times are in GMT).
>
> Is that normal output indicating that btrfs is repairing the
> "staleness" of sdk from the other copy?
Yes, exactly. That output you pasted looks pretty much exactly like
what I'd expect to see in the situation described above. You might
also expect to see some checksum errors corrected in the data, as well
as the metadata messages you're getting.
> I seem to be able to use the filesystem and a cursory inspection
> isn't turning up anything that I can't read or that seems
> corrupted. I will now run checksums against my last good backup.
>
> Should I run a scrub as well?
Yes. The output you've had so far will be just the pieces that the
FS has tried to read, and where, as a result, it's been able to detect
the out-of-date data. A scrub will check and fix everything.
Hugo.
--
Hugo Mills | My karma has run over my dogma.
hugo@... carfax.org.uk |
http://carfax.org.uk/ |
PGP: 65E74AC0 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-04-01 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 15:11 Is this normal? Should I use scrub? Andy Smith
2015-04-01 15:42 ` Hugo Mills [this message]
2015-04-02 9:58 ` Andy Smith
2015-04-02 10:29 ` 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=20150401154202.GD32078@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=andy@strugglers.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 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.