archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <>
To: Dave Kleikamp <>
Subject: Should we orphan JFS?
Date: Thu, 12 Jan 2023 21:42:03 -0800	[thread overview]
Message-ID: <> (raw)

Hi all,

A while ago we've deprecated reiserfs and scheduled it for removal.
Looking into the hairy metapage code in JFS I wonder if we should do
the same.  While JFS isn't anywhere as complicated as reiserfs, it's
also way less used and never made it to be the default file system
in any major distribution.  It's also looking pretty horrible in
xfstests, and with all the ongoing folio work and hopeful eventual
phaseout of buffer head based I/O path it's going to be a bit of a drag.
(Which also can be said for many other file system, most of them being
a bit simpler, though).

             reply	other threads:[~2023-01-13  5:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13  5:42 Christoph Hellwig [this message]
2023-01-13 13:08 ` Should we orphan JFS? Harald Arnesen
2023-01-13 15:06   ` Dave Kleikamp
2023-01-14 12:09     ` Andreas Dilger
2023-01-19  8:05       ` [Jfs-discussion] " Stefan Tibus
2023-02-20 11:45         ` me

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).