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 A7BBEEC8742 for ; Thu, 7 Sep 2023 17:38:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244853AbjIGRio convert rfc822-to-8bit (ORCPT ); Thu, 7 Sep 2023 13:38:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55808 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244709AbjIGRil (ORCPT ); Thu, 7 Sep 2023 13:38:41 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9442990 for ; Thu, 7 Sep 2023 10:38:19 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8D2CFC116B8; Thu, 7 Sep 2023 11:17:47 +0000 (UTC) Date: Thu, 7 Sep 2023 07:18:01 -0400 From: Steven Rostedt To: Dave Chinner Cc: Guenter Roeck , Christoph Hellwig , ksummit@lists.linux.dev, linux-fsdevel@vger.kernel.org Subject: Re: [MAINTAINERS/KERNEL SUMMIT] Trust and maintenance of file systems Message-ID: <20230907071801.1d37a3c5@gandalf.local.home> In-Reply-To: References: <8718a8a3-1e62-0e2b-09d0-7bce3155b045@roeck-us.net> <20230906215327.18a45c89@gandalf.local.home> <20230906225139.6ffe953c@gandalf.local.home> X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Thu, 7 Sep 2023 13:38:40 +1000 Dave Chinner wrote: > Hence, IMO, gutting a filesystem implementation to just support > read-only behaviour "to prolong it's support life" actually makes > things worse from a maintenance and testing persepective, not > better.... >From your other email about 10 years support, you could first set a fs to read-only, and then after so long (I'm not sure 10 years is really necessary), then remove it. That is, make it the stage before removal. If no one complains about it being read-only after several years, then it's highly likely that no one is using it. If someone does complain, you can tell them to either maintain it, or start moving all their data to another fs. For testing, you could even have an #ifdef that needs to be manually changed (not a config option) to make it writable. -- Steve