From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9940BC433EF for ; Mon, 4 Apr 2022 10:58:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1359016AbiDDLA3 (ORCPT ); Mon, 4 Apr 2022 07:00:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40526 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1358911AbiDDLA0 (ORCPT ); Mon, 4 Apr 2022 07:00:26 -0400 Received: from jabberwock.ucw.cz (jabberwock.ucw.cz [46.255.230.98]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 38BCCC24; Mon, 4 Apr 2022 03:58:30 -0700 (PDT) Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id D52F21C0B66; Mon, 4 Apr 2022 12:58:28 +0200 (CEST) Date: Mon, 4 Apr 2022 12:58:28 +0200 From: Pavel Machek To: Willy Tarreau Cc: Jan Kara , Matthew Wilcox , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, reiserfs-devel@vger.kernel.org Subject: Re: Is it time to remove reiserfs? Message-ID: <20220404105828.GA7162@duo.ucw.cz> References: <20220222100408.cyrdjsv5eun5pzij@quack3.lan> <20220402105454.GA16346@amd> <20220404085535.g2qr4s7itfunlrqb@quack3.lan> <20220404100732.GB1476@duo.ucw.cz> <20220404101802.GB8279@1wt.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: <20220404101802.GB8279@1wt.eu> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > But I believe userbase is bigger than you think and it will not be > > possible to remove reiserfs anytime soon. >=20 > I was about to say the opposite until I noticed that one of my main > dev machine has its kernel git dir on it because it's an old FS from > a previous instance of this machine before an upgrade and it turns out > that this FS still had lots of available space to store git trees > :-/ :-). > So maybe you're right and there are still a bit more than expected out > there. However I really think that most users who still have one are in > the same situation as I am, they're not aware of it. So aside big fat > warnings at mount time (possibly with an extra delay), there's nothing > that will make that situation change. >=20 > At the very least disabling it by default in Kconfig and in distros > should be effective. I really don't think that there are still users > who regularly update their system and who have it on their rootfs, but > still having data on it, yes, possibly. The earlier they're warned, > the better. I guess we should start by making sure that distributions don't use it by default. Big fat warning + delay is a bit harsh for that, talking to them should be enough at this point :-). Someone start with Arch Linux ARM. Pavel --=20 People of Russia, stop Putin before his war on Ukraine escalates. --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRPfPO7r0eAhk010v0w5/Bqldv68gUCYkrPVAAKCRAw5/Bqldv6 8g5wAKCDB3UaDOu3F7C3rsVOlJEEkyYU7wCgtmRSLlZxl4muNPrcFe98v6ML2GU= =akzK -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--