From: Christoph Hellwig <hch@infradead.org>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: Eric Sandeen <esandeen@redhat.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org, Dave Chinner <dchinner@redhat.com>,
linuxppc-dev@lists.ozlabs.org,
Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: [PATCH] xfs: introduce "metasync" api to sync metadata to fsblock
Date: Mon, 14 Oct 2019 01:40:27 -0700 [thread overview]
Message-ID: <20191014084027.GA3593@infradead.org> (raw)
In-Reply-To: <1570977420-3944-1-git-send-email-kernelfans@gmail.com>
On Sun, Oct 13, 2019 at 10:37:00PM +0800, Pingfan Liu wrote:
> When using fadump (fireware assist dump) mode on powerpc, a mismatch
> between grub xfs driver and kernel xfs driver has been obsevered. Note:
> fadump boots up in the following sequence: fireware -> grub reads kernel
> and initramfs -> kernel boots.
This isn't something new. To fundamentally fix this you need to
implement (in-memory) log recovery in grub. That is the only really safe
long-term solutioin. But the equivalent of your patch you can already
get by freezing and unfreezing the file system using the FIFREEZE and
FITHAW ioctls. And if my memory is serving me correctly Dave has been
preaching that to the bootloader folks for a long time, but apparently
without visible results.
next prev parent reply other threads:[~2019-10-14 8:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 14:37 [PATCH] xfs: introduce "metasync" api to sync metadata to fsblock Pingfan Liu
2019-10-13 16:34 ` Darrick J. Wong
2019-10-14 8:33 ` Pingfan Liu
2019-10-14 9:43 ` Jan Kara
2019-10-14 13:23 ` Eric Sandeen
2019-10-14 20:03 ` Jan Kara
2019-10-14 20:09 ` Eric Sandeen
2019-10-15 8:01 ` Christoph Hellwig
2019-10-15 13:10 ` Theodore Y. Ts'o
2019-10-15 16:18 ` Darrick J. Wong
2019-10-15 2:20 ` Pingfan Liu
2019-10-15 2:12 ` Pingfan Liu
2019-10-14 8:40 ` Christoph Hellwig [this message]
2019-10-15 1:56 ` Pingfan Liu
2019-10-15 8:01 ` Christoph Hellwig
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=20191014084027.GA3593@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=esandeen@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=kernelfans@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).