From: Dave Chinner <david@fromorbit.com>
To: Fanael Linithien <fanael4@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Metadata CRC error upon unclean unmount
Date: Thu, 26 Jun 2014 09:22:22 +1000 [thread overview]
Message-ID: <20140625232222.GS4453@dastard> (raw)
In-Reply-To: <CA+o=1OWptqFq87E0ncmYH2T6yEzeGheefE-o_VAm7-E_0Z+NJA@mail.gmail.com>
On Thu, Jun 26, 2014 at 12:33:06AM +0200, Fanael Linithien wrote:
> 2014-06-26 0:03 GMT+02:00 Dave Chinner <david@fromorbit.com>:
> > Can you try to reproduce the AGI or AGF/freespace corruption issue
> > and post the results?
>
> Sure, looks like the bug heard you and decided to manifest itself right now.
>
> dmesg: https://clbin.com/g52eu (the second mount error is because I
> typo'd and tried to mount wrong partition)
> Metadata before an attempt to mount: https://clbin.com/YDZBV
Curious. Completely clean log. head/tail at 2/16292. Yet the AGF
head and a couple of btree blocks are have bad CRCs. They were on
disk *before* the system crashed.
> Metadata after an attempt to mount: https://clbin.com/2jayF
Dirty log. tail at 2/16292, head at 2/16332.
The before-mount image shows the CRC error, so it didn't come from
log recovery. It may have come from recovery in the previous
iteration, - do you still have the pre-mount images from the prior
iteration before the crash error was detected?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-25 23:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 16:01 Metadata CRC error upon unclean unmount Fanael Linithien
2014-06-24 16:04 ` Grozdan
2014-06-24 16:08 ` Eric Sandeen
2014-06-24 16:19 ` Fanael Linithien
2014-06-24 16:24 ` Eric Sandeen
2014-06-24 16:37 ` Fanael Linithien
2014-06-24 18:48 ` Eric Sandeen
2014-06-24 19:00 ` Fanael Linithien
2014-06-24 19:45 ` Eric Sandeen
2014-06-24 20:19 ` Dave Chinner
2014-06-24 20:44 ` Fanael Linithien
2014-06-24 21:50 ` Fanael Linithien
2014-06-25 1:21 ` Dave Chinner
2014-06-25 15:28 ` Fanael Linithien
2014-06-25 16:09 ` Fanael Linithien
2014-06-25 22:03 ` Dave Chinner
2014-06-25 22:33 ` Fanael Linithien
2014-06-25 23:22 ` Dave Chinner [this message]
2014-06-25 23:32 ` Fanael Linithien
2014-06-25 23:52 ` Dave Chinner
2014-06-26 0:28 ` Dave Chinner
2014-06-26 2:23 ` Dave Chinner
2014-06-26 20:03 ` Mark Tinguely
2014-06-26 22:47 ` Dave Chinner
2014-06-27 14:26 ` Mark Tinguely
2014-06-28 0:49 ` Dave Chinner
2014-06-29 16:19 ` Mark Tinguely
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=20140625232222.GS4453@dastard \
--to=david@fromorbit.com \
--cc=fanael4@gmail.com \
--cc=xfs@oss.sgi.com \
/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.