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 X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 21D87C4320A for ; Wed, 28 Jul 2021 19:14:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 10B7B60EFD for ; Wed, 28 Jul 2021 19:14:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230228AbhG1TOe (ORCPT ); Wed, 28 Jul 2021 15:14:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49096 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229542AbhG1TOe (ORCPT ); Wed, 28 Jul 2021 15:14:34 -0400 Received: from fieldses.org (fieldses.org [IPv6:2600:3c00:e000:2f7::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8BBB5C061757; Wed, 28 Jul 2021 12:14:32 -0700 (PDT) Received: by fieldses.org (Postfix, from userid 2815) id 7D8237C6F; Wed, 28 Jul 2021 15:14:31 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.11.0 fieldses.org 7D8237C6F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fieldses.org; s=default; t=1627499671; bh=eLHyd9f1nxMzdFMQUYsbq1YAVKzyuU/thj/3IlS+rN8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=GI/8MLOOvbWzAw3TGd39dplxrahRkVMDJve9j0rIzSxMgxbkYgIPJU2RNA+20tvV6 +DbMjnPmh5Fezu+2M1UBC6L1yzcCBJNU1HbTceFM/t6ha5GZmx1lrLbnfXdoCyKHIy 22WjvHwX9xsQc7ezqpGMeDw/SXBu6Yti3hc+XT14= Date: Wed, 28 Jul 2021 15:14:31 -0400 From: "J. Bruce Fields" To: Neal Gompa Cc: NeilBrown , Wang Yugui , Christoph Hellwig , Josef Bacik , Chuck Lever , Chris Mason , David Sterba , Alexander Viro , linux-fsdevel , linux-nfs@vger.kernel.org, Btrfs BTRFS Subject: Re: [PATCH/RFC 00/11] expose btrfs subvols in mount table correctly Message-ID: <20210728191431.GA3152@fieldses.org> References: <162742539595.32498.13687924366155737575.stgit@noble.brown> <20210728125819.6E52.409509F4@e16-tech.com> <20210728140431.D704.409509F4@e16-tech.com> <162745567084.21659.16797059962461187633@noble.neil.brown.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Wed, Jul 28, 2021 at 08:26:12AM -0400, Neal Gompa wrote: > I think this is behavior people generally expect, but I wonder what > the consequences of this would be with huge numbers of subvolumes. If > there are hundreds or thousands of them (which is quite possible on > SUSE systems, for example, with its auto-snapshotting regime), this > would be a mess, wouldn't it? I'm surprised that btrfs is special here. Doesn't anyone have thousands of lvm snapshots? Or is it that they do but they're not normally mounted? --b.