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=-5.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 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 6AE4FC433B4 for ; Wed, 5 May 2021 13:59:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 24DF06101C for ; Wed, 5 May 2021 13:59:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233423AbhEEOAC (ORCPT ); Wed, 5 May 2021 10:00:02 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:57313 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232923AbhEEOAC (ORCPT ); Wed, 5 May 2021 10:00:02 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 69E565C0187; Wed, 5 May 2021 09:59:05 -0400 (EDT) Received: from imap5 ([10.202.2.55]) by compute3.internal (MEProxy); Wed, 05 May 2021 09:59:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=georgianit.com; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=1B/MDieHYAtaNQggohZ0z7I28qMBXpS BHKSutPMqhKc=; b=KmuJeqvcQAcoa5yFwwX9YoK9IveSFAn3337l281GYHGcsp/ 6mSg+Hr2sep5FDD17Rp+Z90q6a4IqEO2xSt2ggBB1Q22QbjblI91k2PblkMqIwu2 Wx84ZpVTmBXEHPgtsVGIczMLM/Y8e4/t3HaAsHdAMS2DZN0vLG+ix+W51V30PjK/ itUqsnkW7jczZ1N5977rAJNW9+vqH0C0pKq5j4MnxPMTAIRRrw1cx6+/urOyrrRm TtujGLxkxzjpv2AmEJM+c8bWSC9isqasssTsND7cKmpXrxoNv5UeB9blFPebzfWw TKd6s3s4VvhL/hVp/Q8H1XJMmKNJ0sEh9nurTtw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=1B/MDi eHYAtaNQggohZ0z7I28qMBXpSBHKSutPMqhKc=; b=KCHI1SX4gYVUukYX+3zCjn UhzRgDiIXL+vrSkdFspvNItsWA6cKXoF/Hv5EaAYrDV6M2hEEeNrY9DU7qo5mX+p nQ2zs1whP+4N3/5ZMMKGFiYlS3ZZ+ufsiVRMujZSxjqlad+cdjOPT9SQGUf8vaR6 HN+TyO0VNXt0hUVbBZenu0IImN4SRVRKSStHn2jCrY6dlQRF/9bJi/OlDho+xbD9 QirkomIE7ILQtXma1a3RuDth7w4oGgFVrSW2J4vZoxbRvnNGvAiHpsK+aYICtiXH 7cgYZYIEAqKI3OCsW5K+8YiopdLPKbvZUfcdfKiMWsmo/ro4IQ3YzenkbjP9yRXQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdefkedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpehrvghmihesghgvohhrghhirghnihhtrdgtohhmnecuggft rfgrthhtvghrnhepuefgfeevgfduffekudfhledvieeffeelgfekgeelffdvkeelvdekgf dvudejffegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhho mheprhgvmhhisehgvghorhhgihgrnhhithdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3969BA0085; Wed, 5 May 2021 09:59:05 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-442-g5daca166b9-fm-20210428.001-g5daca166 Mime-Version: 1.0 Message-Id: <5b563f2f-9057-44cc-8ec8-5367548aef6f@www.fastmail.com> In-Reply-To: References: Date: Wed, 05 May 2021 09:58:03 -0400 From: remi@georgianit.com To: "Abdulla Bubshait" , linux-btrfs@vger.kernel.org Subject: Re: Array extremely unbalanced after convert to Raid5 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Wed, May 5, 2021, at 9:41 AM, Abdulla Bubshait wrote: > I ran a balance convert of my data single setup to raid 5. Once > complete the setup is extremely unbalanced and doesn't even make sense > as a raid 5. I tried to run a balance with dlimit of 1000, but it just > seems to make things worse. > > Unallocated: > /dev/sdd 14.12TiB > /dev/sdc 404.99GiB > /dev/sdf 1.00MiB > /dev/sde 1.00MiB > > Sorry, I don't have a solution for you, but I want to point out that the situation is far more critical than you seem to have realized.. this filesystem is now completely wedged, and I would suggest adding another device, or replacing either /dev/sdf or /dev/sde with something larger,, (though, if those are real disks, I see that might be a challenge.) Your metadata is Raid1C3, (meaning 3 copies,), but you only have 2 disks with free space. And thanks to the recent balancing, there is very little free space in the already allocated metadata,, so effectively, the filesystem can no longer write any new metadata and will very quickly hit out of space errors.