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 475FDC433F5 for ; Fri, 25 Feb 2022 13:10:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240964AbiBYNLA (ORCPT ); Fri, 25 Feb 2022 08:11:00 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56112 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233784AbiBYNKz (ORCPT ); Fri, 25 Feb 2022 08:10:55 -0500 Received: from winds.org (winds.org [68.75.195.9]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 3B2931E7A43; Fri, 25 Feb 2022 05:10:23 -0800 (PST) Received: by winds.org (Postfix, from userid 100) id 8F7521CA5924; Fri, 25 Feb 2022 08:10:22 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by winds.org (Postfix) with ESMTP id 8D2511CA5920; Fri, 25 Feb 2022 08:10:22 -0500 (EST) Date: Fri, 25 Feb 2022 08:10:22 -0500 (EST) From: Byron Stanoszek To: Matthew Wilcox cc: Dave Chinner , Jan Kara , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, reiserfs-devel@vger.kernel.org Subject: Re: Is it time to remove reiserfs? In-Reply-To: Message-ID: <257dc4a9-dfa0-327e-f05a-71c0d9742e98@winds.org> References: <20220222100408.cyrdjsv5eun5pzij@quack3.lan> <20220222221614.GC3061737@dread.disaster.area> <3ce45c23-2721-af6e-6cd7-648dc399597@winds.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 24 Feb 2022, Matthew Wilcox wrote: > On Wed, Feb 23, 2022 at 09:48:26AM -0500, Byron Stanoszek wrote: >> For what it's worth, I have a number of production servers still using >> Reiserfs, which I regularly maintain by upgrading to the latest Linux kernel >> annually (mostly to apply security patches). I figured this filesystem would >> still be available for several more years, since it's not quite y2038k yet. > > Hey Byron, thanks for sharing your usage. > > It's not entirely clear to me from your message whether you're aware > that our annual LTS release actually puts out new kernels every week (or > sometimes twice a week), and upgrades to the latest version are always > recommended. Those LTS kernels typically get five years of support in > total; indeed we just retired the v4.4 series earlier this month which > was originally released in January 2016, so it got six years of support. > > If we dropped reiserfs from the kernel today (and thanks to Edward, we > don't have to), you'd still be able to use a v5.15 based kernel with > regular updates until 2028. If we drop it in two years, that should > take you through to 2030. Is that enough for your usage? I'm aware of the LTS releases, but I hadn't thought about them in relation to this issue. That's a good point, and so it sounds like I have nothing to worry about. Thanks for the recommendation. Regards, -Byron