linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Thomas Dreibholz <dreibh@simula.no>
Cc: gandalf@winds.org, david@fromorbit.com, jack@suse.cz,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	reiserfs-devel@vger.kernel.org, willy@infradead.org
Subject: Re: Is it time to remove reiserfs?
Date: Thu, 17 Mar 2022 10:43:44 +0100	[thread overview]
Message-ID: <20220317094344.5s3shqk54qfpumey@quack3.lan> (raw)
In-Reply-To: <842c582a-ecb6-31a1-fad1-54a4e9c05b94@simula.no>

Hi!

On Thu 17-03-22 09:53:22, Thomas Dreibholz wrote:
> I just noticed the thread about ReiserFS deprecation. We are currently still
> using ReiserFS on ca. 50 production machines of the NorNet Core
> infrastructure (https://www.nntb.no/). While newer machines use BTRFS
> instead, the older machines had ReiserFS used, due to its stability and
> better performance in comparison to ext4. At their installation time, we did
> not consider BTRFS being mature enough. A deprecation period of ca. 5 years
> from now seems to be reasonable, although it would be nice to have at least
> a read-only capability available for some longer time, for the case it
> becomes necessary to read an old ReiserFS file system on a newer system.

Thanks for your feedback! So the current plan is to remove the support from
current upstream kernel in ~3 years, as people noted, you can still use
upstream -stable kernels branched at the end of the deprecation period for
another two years which gives you around 5 years to migrate if you are
using upstream stable kernels. 

You can still use sufficiently old kernel (VM?) or FUSE (although someone
motivated would probably need to write proper support module but e.g. grub2
has reiserfs support in userspace implemented) to get data out of
Reiserfs partitions after that... At least that's the current plan.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2022-03-17  9:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 12:13 Is it time to remove reiserfs? Matthew Wilcox
2022-02-20 23:21 ` Edward Shishkin
2022-02-20 23:22   ` [PATCH] reiserfs: get rid of AOP_FLAG_CONT_EXPAND flag Edward Shishkin
2022-02-22 10:27     ` Jan Kara
2022-02-22 13:38       ` Matthew Wilcox
2022-02-23 12:17         ` Jan Kara
2022-02-22 10:04 ` Is it time to remove reiserfs? Jan Kara
2022-02-22 22:16   ` Dave Chinner
2022-02-23 14:48     ` Byron Stanoszek
2022-02-23 15:28       ` Byron Stanoszek
2022-03-17  8:53         ` Thomas Dreibholz
2022-03-17  9:43           ` Jan Kara [this message]
2022-02-24  8:46       ` Jan Kara
2022-02-24 14:24         ` Byron Stanoszek
2022-02-24 21:06       ` Matthew Wilcox
2022-02-25 13:10         ` Byron Stanoszek
2022-02-25 13:23           ` Willy Tarreau
2022-02-25 22:56             ` Dave Chinner
2022-02-26  0:00               ` Theodore Ts'o
2022-04-02 10:57     ` Pavel Machek
2022-04-05 23:04       ` Dave Chinner
2022-04-02 10:54   ` Pavel Machek
2022-04-04  8:55     ` Jan Kara
2022-04-04 10:07       ` Pavel Machek
2022-04-04 10:18         ` Willy Tarreau
2022-04-04 10:58           ` Pavel Machek
2022-04-04 13:05             ` Jan Kara
2022-04-04 12:55           ` Jan Kara
2022-04-04 13:16             ` Willy Tarreau

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=20220317094344.5s3shqk54qfpumey@quack3.lan \
    --to=jack@suse.cz \
    --cc=david@fromorbit.com \
    --cc=dreibh@simula.no \
    --cc=gandalf@winds.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=willy@infradead.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).