From patchwork Sat Apr 4 10:32:12 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Goffredo Baroncelli X-Patchwork-Id: 11474187 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 06ED4912 for ; Sat, 4 Apr 2020 10:32:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D9BCE2072B for ; Sat, 4 Apr 2020 10:32:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=libero.it header.i=@libero.it header.b="AoTqIbq+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726272AbgDDKcV (ORCPT ); Sat, 4 Apr 2020 06:32:21 -0400 Received: from smtp-16-i2.italiaonline.it ([213.209.12.16]:53448 "EHLO libero.it" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726157AbgDDKcU (ORCPT ); Sat, 4 Apr 2020 06:32:20 -0400 Received: from venice.bhome ([94.37.173.46]) by smtp-16.iol.local with ESMTPA id Kg63jDxJE6Q7RKg66jI6Wo; Sat, 04 Apr 2020 12:32:18 +0200 x-libjamoibt: 1601 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=libero.it; s=s2014; t=1585996338; bh=NvzAaTARaLJ96vxBk5dd3zVfmf+EeFgB/b1nhVCFYZU=; h=From; b=AoTqIbq+7jt+9U1Oe3dqFFZmHE/LS9OCmnlK62yGBEGQaSTVUvPsWh1G0iIHWxJxo EQr2X9Kes/lLG2vf2Fcxa6N+Akqd9rs7h4FRo3l2DWsRNMzzkz12zUn0kDwF88awAP eo47prsCKe4u2cJ+6N4UV9CTg0bZz0/B8i4G2878DlbkK3dos2A0wBIgd4gLmlnNKB SfC+2sOA2WPwAfviBc3634X6wmHXhqidkwTk3XIizCGs1jppL1d+GfPkd7bI8eWcf9 8esk+HG5l4+c84r7ZtDvEbMyIXHvEhEm/FcvKUwsLinEk589gizkcJXuEYSlBKMG0m 6g7wPWi6ynX6A== X-CNFS-Analysis: v=2.3 cv=LelCFQXi c=1 sm=1 tr=0 a=TpQr5eyM7/bznjVQAbUtjA==:117 a=TpQr5eyM7/bznjVQAbUtjA==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=T92Z9xJX5iHLdJxoEloA:9 From: Goffredo Baroncelli To: linux-btrfs@vger.kernel.org Cc: Zygo Blaxell , Qu Wenruo , David Sterba , Graham Cobb , Goffredo Baroncelli Subject: [PATCH 5/5] Update the man page in order to give a guideline about mixed profiles. Date: Sat, 4 Apr 2020 12:32:12 +0200 Message-Id: <20200404103212.40986-6-kreijack@libero.it> X-Mailer: git-send-email 2.26.0 In-Reply-To: <20200404103212.40986-1-kreijack@libero.it> References: <20200404103212.40986-1-kreijack@libero.it> MIME-Version: 1.0 X-CMAE-Envelope: MS4wfKAGwLMXXr86U8TsKLPeJGlM+Q5SkBcu5LXuqJE0AUZ3SD8jePIyqFazIUOPNZKtP7UTnBT/YGIHndjwJAVetsrOQ8Cp2j97j7vaQVrpe/4YoqPkcRQc JtFUMFANXp6j0977pueoUYGdoc/cmd53kdzMaqQ3SyLf3tfq+qoPAO51P47QDAOJyabDXcrWovCwKw6/Dod3kPZZCCG2DDvjtaGVETf2mDylX7Y1/cki8mot 71x3cl/Me0b3BfG7wM3s/nCekk9Mniw2FD26Wn7P8+bCkb7FpiaZLhhKFoCPNei2cbHrOX0732vS+D5dMzY7CcLpa59jxw2DgeA5Gn39sgI= Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org From: Goffredo Baroncelli Signed-off-by: Goffredo Baroncelli --- Documentation/btrfs-man5.asciidoc | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/Documentation/btrfs-man5.asciidoc b/Documentation/btrfs-man5.asciidoc index 56b1ed58..88f1c5ed 100644 --- a/Documentation/btrfs-man5.asciidoc +++ b/Documentation/btrfs-man5.asciidoc @@ -846,6 +846,37 @@ work and a workaround would need to be used to mount a multi-device filesystem. The mount option 'device' can trigger the device scanning during mount. +FILESYSTEM WITH MULTIPLE PROFILES +--------------------------------- + +It is possible that a btrfs filesystem features block group of the same +type (e.g. data) with different profiles. +This could happen when a profile conversion is interrupted (see +`btrfs-balance(8)`). +Some 'btrfs' commands perform a test to detect this kind of condition. In such +case a warning like this is showed: + +-------------------- +WARNING: Multiple profiles detected. See 'man btrfs(5)'. +WARNING: data -> [raid1, single], metadata -> [raid1, single] +-------------------- + +In a case like this, it is suggested to complete the conversion running +`btrfs balance`. This because the next block group allocation +is performed on the basis of the set of the profiles present on the disks, +according to the following priorities: + +* RAID6 +* RAID5 +* RAID10 +* RAID1 +* RAID0 + +For example if both the profile RAID6 and RAID1 are present on the disks, +the next block group allocation will be RAID6, regardeless of the last +`btrfs balance`. + + SEE ALSO -------- `acl`(5),