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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 22E2DC3F2D2 for ; Mon, 2 Mar 2020 07:39:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DEC0D246B9 for ; Mon, 2 Mar 2020 07:39:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=wpkg.org header.i=@wpkg.org header.b="PbVOhFJ1" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726621AbgCBHjW (ORCPT ); Mon, 2 Mar 2020 02:39:22 -0500 Received: from mail.virtall.com ([46.4.129.203]:45290 "EHLO mail.virtall.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725446AbgCBHjW (ORCPT ); Mon, 2 Mar 2020 02:39:22 -0500 Received: from mail.virtall.com (localhost [127.0.0.1]) by mail.virtall.com (Postfix) with ESMTP id 4F3DB3F6FDE0; Mon, 2 Mar 2020 07:39:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wpkg.org; s=default; t=1583134761; bh=x9Yj/lrrjJiEQOlx2LI5NEp4dLxxxz8qvMMVNo8Yyr4=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=PbVOhFJ1HxBOqY/OnAN2GV18T8De3pA2jtSIkRt+4tPkn+kTRrqvVmKt/M4K3pOvV 6LMzvRy8gKR9CQXGqz0qd3u0BJdPOQbn7nLppSZyiV2NnR19/QxBCQHqs7VZ7hDikC F4dvYq2cAjfjl47jNm7gkDkq77UGo6G5WS/1f7qukfFeXjeyTglHxY9PmADT12VNvG O88VaxGpJPVUr62solZZg94J9sABOw8gGKbKNsVjs+kb4b1ray9c/ZQ9aSge0JD5OK qUyhhfaEEji+gPgy3PK6NVz68vOEwSTro3RBZW7Fl+A1OoAzh2YJNEPDXMDejvE2Sm LtEn5WQ1LHudA== X-Fuglu-Suspect: 5e09132893cb4360a497d5c68d91309c X-Fuglu-Spamstatus: NO Received: from localhost (localhost [127.0.0.1]) (Authenticated sender: tch@virtall.com) by mail.virtall.com (Postfix) with ESMTPSA; Mon, 2 Mar 2020 07:39:20 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 02 Mar 2020 16:39:17 +0900 From: Tomasz Chmielewski To: Chris Murphy Cc: Btrfs BTRFS Subject: Re: balance conversion from RAID-1 to RAID-10 leaves some metadata in RAID-1? In-Reply-To: References: <56ef4bcdd854a9dde3cbe2f5760592ed@wpkg.org> Message-ID: X-Sender: mangoo@wpkg.org Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On 2020-03-02 15:29, Chris Murphy wrote: > On Sun, Mar 1, 2020 at 3:41 AM Tomasz Chmielewski > wrote: >> >> To my surprise, some metadata is still RAID-1 - is it expected? > > I'd say it's not expected but also balance is pretty complicated. Try > > 'btrfs balance start -dconvert=raid10,soft /mountpoint/' > > What does dmesg report for that command? And are those raid1 bg's > converted to raid10? I don't think it should matter in this case, but > what's the btrfs-progs version? I did one more balance, for metadata only: btrfs balance start -dconvert=raid10 /mountpoint/ And it fully converted the remaining RAID-1 metadata to RAID-10. Still, a bit "weird". btrfs-progs is 5.4.1. Tomasz Chmielewski https://lxadm.com