public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: XFS: corruption detected in 5.9.10, upgrading from 5.9.6: (partial) panic log
Date: Sun, 22 Nov 2020 20:14:24 +0000	[thread overview]
Message-ID: <87ft51m9nj.fsf@esperi.org.uk> (raw)
In-Reply-To: <20201122193711.GA7880@magnolia> (Darrick J. Wong's message of "Sun, 22 Nov 2020 11:37:11 -0800")

On 22 Nov 2020, Darrick J. Wong stated:

> On Sun, Nov 22, 2020 at 06:38:28PM +0000, Nick Alcock wrote:
>> So I just tried to reboot my x86 server box from 5.9.6 to 5.9.10 and my
>
> Sorry about that, there was a bad patch in -rc4 that got sucked into
> 5.9.9 because it had a fixes tag.  The revert is already upstream:
>
> https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/commit/?id=eb8409071a1d47e3593cfe077107ac46853182ab

Thanks! Will give it a try soon :)

(Solved in a couple of hours on a Sunday and all I had to do was mail
off a photo. As I always say about free software, especially while
feeling guilty about my own response times... you can't pay for service
like this!)

... and no I don't know why I didn't think to check the master branch
for obvious related reversions in fs/xfs. I'll do that next time before
bothering other people.

      reply	other threads:[~2020-11-22 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22 18:38 XFS: corruption detected in 5.9.10, upgrading from 5.9.6: (partial) panic log Nick Alcock
2020-11-22 19:37 ` Darrick J. Wong
2020-11-22 20:14   ` Nick Alcock [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=87ft51m9nj.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=darrick.wong@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox