linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@dilger.ca>
To: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: Harald Arnesen <harald@skogtun.org>,
	Christoph Hellwig <hch@infradead.org>,
	jfs-discussion@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Should we orphan JFS?
Date: Sat, 14 Jan 2023 05:09:10 -0700	[thread overview]
Message-ID: <393B8E4A-8C9A-4941-9AFF-FAC9C0D0B2DA@dilger.ca> (raw)
In-Reply-To: <f99e5221-4493-dba3-3e80-e85ada6b3545@oracle.com>

On Jan 13, 2023, at 08:15, Dave Kleikamp <dave.kleikamp@oracle.com> wrote:
> 
> On 1/13/23 7:08AM, Harald Arnesen wrote:
>> Christoph Hellwig [13/01/2023 06.42]:
>>> 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).
>> The Norwegian ISP/TV provider used to have IPTV-boxes which had JFS on the hard disk that was used to record TV programmes.
>> However, I don't think these boxes are used anymore.
> 
> I know at one time it was one of the recommended filesystems for MythTV. I don't know of any other major users of JFS. I don't know if there is anyone familiar with the MythTV community that could weigh in.
> 
> Obviously, I haven't put much effort into JFS in a long time and I would not miss it if it were to be removed.

I've used MythTV for many years but haven't seen any particular recommendations for JFS there. Mainly ext4 and XFS are the common filesystems to follow the main distros (Ubuntu in particular). 

Cheers, Andreas

  reply	other threads:[~2023-01-14 12:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13  5:42 Should we orphan JFS? Christoph Hellwig
2023-01-13 13:08 ` Harald Arnesen
2023-01-13 15:06   ` Dave Kleikamp
2023-01-14 12:09     ` Andreas Dilger [this message]
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:
  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=393B8E4A-8C9A-4941-9AFF-FAC9C0D0B2DA@dilger.ca \
    --to=adilger@dilger.ca \
    --cc=dave.kleikamp@oracle.com \
    --cc=harald@skogtun.org \
    --cc=hch@infradead.org \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).