From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] bootfs: simple bootloader filesystem
Date: Tue, 2 Apr 2019 08:46:32 +1100 [thread overview]
Message-ID: <20190401214632.GS26298@dastard> (raw)
In-Reply-To: <20190401070001.GJ1173@magnolia>
On Mon, Apr 01, 2019 at 12:00:01AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Does your computer use a bootloader which arrogantly declares that it can
> read boot files off a filesystem but isn't sophisticated enough even to
> recognize when that filesystem needs journal recovery?
>
> Does your system software deployment program foolishly omit system calls
> to flush newly unwrapped packages to disk? Do you sometimes wonder if
> they've forgotten that old maxim, "wait for the disk drive light to turn
> off /before/ you power down"?
>
> Are your computer operators aggressively derpy? Do they have a habit of
> leaving disk cables on the floor so they can trip over them twenty times
> a day? Does this leave you with sad files full of zeroes?
>
> If so, bootfs is for you! This new filesystem type uses journalling to
> ensure metadata integrity, but forces all writes and directory tree
> updates to be synchronous, fsyncs files on close, and checkpoints its
> journal whenever a synchronization event happens. Some allege this is
> very slow, but I've been able to max out the iops on both of my double
> height floppy drives! In a power-cycling stress test, I found that the
> switch broke off in my hand before I lost any data. This concept may
> sound terrible, but like any good crutch, it _is_ made of wood!
>
> Singed-off-by: Darrick J. Wong <djwong@kernel.org>
^^^^^^^^^^
Ooooo - such a hot topic! Finally bootfs is more than just
we-really-should-do-this conference talk!
Looks good to me - with this we can finally move on from LILO....
Acked-by: Dave Chinner <david@fromorbit.com>
FWIW, Should this have a cc: stable@kernel.org tag on
it so it gets out into distro-world ASAP?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-04-01 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 7:00 [PATCH] bootfs: simple bootloader filesystem Darrick J. Wong
2019-04-01 7:01 ` [PATCH] e2fsprogs: create tools for formatting and fscking bootfs Darrick J. Wong
2019-04-01 21:46 ` Dave Chinner [this message]
2019-04-02 4:55 ` [PATCH] bootfs: simple bootloader filesystem Darrick J. Wong
2019-04-02 21:52 ` Andreas Dilger
2019-04-02 22:22 ` Darrick J. Wong
2019-04-06 23:27 ` Theodore Ts'o
2019-04-07 18:10 ` Eric Sandeen
2019-04-07 20:13 ` Darrick J. Wong
2019-04-07 21:13 ` Eric Sandeen
2019-04-08 11:28 ` Andreas Dilger
2019-04-09 3:23 ` Darrick J. Wong
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=20190401214632.GS26298@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).