From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Jan Kara <jack@suse.cz>, Eric Sandeen <esandeen@redhat.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Jan Kara <jack@suse.com>, Pingfan Liu <kernelfans@gmail.com>,
linux-xfs@vger.kernel.org, Dave Chinner <dchinner@redhat.com>,
linux-fsdevel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: [PATCH] xfs: introduce "metasync" api to sync metadata to fsblock
Date: Tue, 15 Oct 2019 01:01:02 -0700 [thread overview]
Message-ID: <20191015080102.GB3055@infradead.org> (raw)
In-Reply-To: <5796090e-6206-1bd7-174e-58798c9af052@sandeen.net>
On Mon, Oct 14, 2019 at 03:09:48PM -0500, Eric Sandeen wrote:
> We're in agreement here. ;) I only worry about implementing things like this
> which sound like guarantees, but aren't, and end up encouraging bad behavior
> or promoting misconceptions.
>
> More and more, I think we should reconsider Darrick's "bootfs" (ext2 by another
> name, but with extra-sync-iness) proposal...
Having a separate simple file system for the boot loader makes a lot of
sense. Note that vfat of EFI is the best choice, but at least it is
something. SysV Unix from the 90s actually had a special file system just
for that, and fs/bfs/ in Linux supports that. So this isn't really a new
thing either.
next prev parent reply other threads:[~2019-10-15 8:03 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 [this message]
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
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=20191015080102.GB3055@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=jack@suse.com \
--cc=jack@suse.cz \
--cc=kernelfans@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sandeen@sandeen.net \
/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).