Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp136700pxm; Fri, 25 Feb 2022 05:24:22 -0800 (PST) X-Google-Smtp-Source: ABdhPJyTgZOX53aenTELL2+QNOsmOiNQwlT0/TB9QFY3BSTf5xpEEynqfn5wqlHYvZMuDDM7zcnN X-Received: by 2002:a17:90a:1202:b0:1b9:b7e7:1652 with SMTP id f2-20020a17090a120200b001b9b7e71652mr3205509pja.1.1645795462571; Fri, 25 Feb 2022 05:24:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645795462; cv=none; d=google.com; s=arc-20160816; b=Gx6QI9LwP7J3zLYowNNXFIcJN4n6m7zwwldPRc4AkskR0DOjz329BWSQtwjvq+gSdW RNlG+rlgJs/QfUtkU34NGbnpNlJacX+3AW17JoBh7ubFeuqwA57c15wQ+h9f41sAzt+6 bcYGTPosTGUUzMnInK6UHyWEWvzE2H053dntVZ1bhVncjqGA4HYv/EN8kt2V+oE/BA+a mbvti6+JnUHVSr1zcZTcOOJDCzJL81USkrwZP9Tc59FzPMkyHDdEALIKcgLSNpYENOW+ +POXqY45JSmxHlq2AdcLE1DXT3Jm7Cqv1HEh8qhJiRYzEdv4LjfSU21moFR3c31fa0DF ZJXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date; bh=ThOBbHAz8teIe1qJbJq6Dfae+0GsG41JXkKEnAjP7+4=; b=Bl5lw+mix0COZ+OKqwE+EXv3tkQWgSQb36SPvi0aplrlrSga41NKuZGT80GxTm5YpW 8EbkPVnvcPfQq3h5aJVY5MT9FOXs/Yvdib0Ay3fOf4psprfDPyLOpQDQjY5pa3RFE5cj PImmpVUVWOQmitZjYXqTkozYE0yFeocoVtbSK2HvgoaF6LJdynH6wuwjgXOdQYCOCZPA qpILA+pAJ01R1L5sRsryDLYqAAgG7W/13FzetfA30SgOSk/FsjVqy7/YNQ4MsYAXOvaa lOrqYYcTR6ACMJBqN3NILPuw3bb23pNYwF3/6OHVU/FLSfytHBvjSBT07RVKtqDUbttF Rrfw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 14-20020a17090a018e00b001b8b32dbd07si7316866pjc.101.2022.02.25.05.24.06; Fri, 25 Feb 2022 05:24:22 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240962AbiBYNK6 (ORCPT + 99 others); Fri, 25 Feb 2022 08:10:58 -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 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net 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