From: Brian Foster <bfoster@redhat.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Dave Chinner <david@fromorbit.com>,
"'linux-xfs@vger.kernel.org'" <linux-xfs@vger.kernel.org>
Subject: Re: Weird xfs_repair error
Date: Tue, 25 Jul 2017 15:22:41 -0400 [thread overview]
Message-ID: <20170725192240.GA57022@bfoster.bfoster> (raw)
In-Reply-To: <20170725191604.43a3691e@harpe.intellique.com>
On Tue, Jul 25, 2017 at 07:16:04PM +0200, Emmanuel Florac wrote:
> Le Mon, 24 Jul 2017 10:51:25 -0400
> Brian Foster <bfoster@redhat.com> écrivait:
>
> > There are several fixes in-flight for the issues uncovered by this
> > metadump. I think you'll want to include the following 3 patches to
> > xfsprogs:
> >
> > http://marc.info/?l=linux-xfs&m=150047977108174&w=2
> > http://marc.info/?l=linux-xfs&m=150040481220074&w=2
> > http://marc.info/?l=linux-xfs&m=150040481820076&w=2
> >
>
> BTW to which branch do these apply?
>
> For some reason I've tried xfs_repair 4.12 on another image I had tried
> 4.7 and 4.9 on, and... it seems to have repaired it. I'm trying to
> understand how that happened...
I believe these should apply to for-next. FWIW, the error in your
previous mail looks like the one that is fixed by the latter two patches
above.
Brian
>
> --
> ------------------------------------------------------------------------
> Emmanuel Florac | Direction technique
> | Intellique
> | <eflorac@intellique.com>
> | +33 1 78 94 84 02
> ------------------------------------------------------------------------
prev parent reply other threads:[~2017-07-25 19:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 13:30 Weird xfs_repair error Emmanuel Florac
2017-07-06 13:48 ` Brian Foster
2017-07-06 14:49 ` Emmanuel Florac
2017-07-06 23:28 ` Dave Chinner
2017-07-07 11:36 ` Emmanuel Florac
2017-07-07 11:50 ` Emmanuel Florac
2017-07-07 15:36 ` Darrick J. Wong
2017-07-10 17:29 ` Emmanuel Florac
2017-07-11 13:23 ` Emmanuel Florac
2017-07-17 17:11 ` Brian Foster
2017-07-24 14:27 ` Emmanuel Florac
2017-07-24 14:51 ` Brian Foster
2017-07-25 16:44 ` Emmanuel Florac
2017-07-25 17:16 ` Emmanuel Florac
2017-07-25 19:22 ` Brian Foster [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=20170725192240.GA57022@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=eflorac@intellique.com \
--cc=linux-xfs@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.