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=-6.8 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_GIT 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 B6C7FC43461 for ; Wed, 9 Sep 2020 21:45:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 319BF205CB for ; Wed, 9 Sep 2020 21:45:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=bur.io header.i=@bur.io header.b="m7QKwu3O"; dkim=temperror (0-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="tsi17ZSB" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726714AbgIIVp3 (ORCPT ); Wed, 9 Sep 2020 17:45:29 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:39339 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726426AbgIIVp0 (ORCPT ); Wed, 9 Sep 2020 17:45:26 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8476A5C0130; Wed, 9 Sep 2020 17:45:25 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 09 Sep 2020 17:45:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bur.io; h=from :to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=fm1; bh=B+Rp/pjVWS/4X58wyOPvLN6u3B CdeTUOJeiuoCKjLpk=; b=m7QKwu3O6k7FQZVNZ0bJSrVjVaNmRIqKEWQ/dot2Gd KkUnDhO0IcfasRyiONspEF2hxaxXLQBWwtiEFjqcyUvYMC6tr7zqxmuJ+PKj8enb CAsyD1BKovkS453ZqkxWTCfHixqsy/CEX43QzueLterbnAEHfDOCL1ec6KZZguch ChBYY5vmyFcSN1UBdfvnqDyEVEobMoC8/MpWCXNHiIVOzqC8L3rr8dOZHlpYNjYH pjKsLmr9IN05eVbvsiEQSPKaeUfyBbmEK9koFc6q5Fqbe5uWbXKULmFjCs+41PCV k82G/YEuPG+PRP9VvHLsEgqAMCdGuWaY1tXXQNxHMwAw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=B+Rp/pjVWS/4X58wy OPvLN6u3BCdeTUOJeiuoCKjLpk=; b=tsi17ZSBcGNrdEV93oAk+UBx9L+zJoXk7 0VT8ewmXXreF3e6563N8ZQquri/Q8R2DfOnXd45ImGoWg0mwNl13P3KKrVkTCv4I InFMCcjCvAIXM1vT1U4YhbwbSLBipG+Jz/heZQDyKa6AtXiuuSga6qDfXAlKFMxt M+2xH6lFxSbLfPazwuh+VVjpMTJGBVr8tk6+HPW+5ZS7pH9EEMYPPbssf9Q3z3ht 4ccRD0rz8ZRVKRHKot6o6rlrrXou3KDnk4Q5S5egt3mpREcLil44N33xZOey6asS 2P5k/UhdfvXLZ8tuTb/89CrgxBcL5G/U5KoL8a81jwX0L02kJCQWg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudehiecutefuodetggdotefrodftvfcurf hrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefhvffufffkofgggfestdekredtredttdenucfhrhhomhepuehorhhishcuuehurhhk ohhvuceosghorhhishessghurhdrihhoqeenucggtffrrghtthgvrhhnpeduiedtleeuie ejfeelffevleeifefgjeejieegkeduudetfeekffeftefhvdejveenucfkphepudeifedr uddugedrudefvddrfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpegsohhrihhssegsuhhrrdhioh X-ME-Proxy: Received: from localhost (unknown [163.114.132.3]) by mail.messagingengine.com (Postfix) with ESMTPA id 047FA3068BF3; Wed, 9 Sep 2020 17:45:25 -0400 (EDT) From: Boris Burkov To: Dave Sterba , Josef Bacik , Chris Mason Cc: Boris Burkov , linux-btrfs@vger.kernel.org, kernel-team@fb.com Subject: [PATCH v2 0/3] btrfs: free space tree mounting fixes Date: Wed, 9 Sep 2020 14:45:15 -0700 Message-Id: X-Mailer: git-send-email 2.24.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org A few fixes for issues with mounting the btrfs free space tree (aka space_cache v2). These are not dependent, and are only related loosely, in that they all apply to mounting the file system with the free space tree. The first patch fixes -o remount,space_cache=v2. The second patch fixes the slight oversight of not cleaning up the space cache free space object or free space inodes when migrating to the free space tree. The third patch stops re-creating the free space objects when we are not using space_cache=v1. changes for v2: Patch 1/3: made remount _only_ work in ro->rw case, added comment. Patch 2/3: added btrfs_ prefix to non-static function, removed bad whitespace. Patch 3/3: new in v2, was part of Patch 2/2 in v1. Boris Burkov (3): btrfs: support remount of ro fs with free space tree btrfs: remove free space items when creating free space tree btrfs: skip space_cache v1 setup when not using it fs/btrfs/block-group.c | 42 ++++---------------------------- fs/btrfs/free-space-cache.c | 48 +++++++++++++++++++++++++++++++++++++ fs/btrfs/free-space-cache.h | 2 ++ fs/btrfs/free-space-tree.c | 3 +++ fs/btrfs/super.c | 29 ++++++++++++++++++++++ 5 files changed, 87 insertions(+), 37 deletions(-) -- 2.24.1