From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [195.159.176.226] ([195.159.176.226]:33500 "EHLO blaine.gmane.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753986AbeE1Id1 (ORCPT ); Mon, 28 May 2018 04:33:27 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fNDYf-0008LA-K0 for linux-btrfs@vger.kernel.org; Mon, 28 May 2018 10:31:13 +0200 To: linux-btrfs@vger.kernel.org From: Duncan <1i5t5.duncan@cox.net> Subject: Re: RAID-1 refuses to balance large drive Date: Mon, 28 May 2018 08:31:06 +0000 (UTC) Message-ID: References: <56F1E7BE.1000004@gmail.com> <56F2C991.9080500@gmail.com> <56F2EA25.4070004@gmail.com> <6dc280f8-3822-078e-9b69-c3203e75ec1e@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: Brad Templeton posted on Sun, 27 May 2018 11:22:07 -0700 as excerpted: > BTW, I decided to follow the original double replace strategy suggested -- > replace 6TB with 8TB and replace 4TB with 6TB. That should be sure to > leave the 2 large drives each with 2TB free once expanded, and thus able > to fully use all space. > > However, the first one has been going for 9 hours and is "189.7% done" > and still going. Some sort of bug in calculating the completion > status, obviously. With luck 200% will be enough? IIRC there was an over-100% completion status bug fixed, I'd guess about 18 months to two years ago now, long enough it would have slipped regular's minds so nobody would have thought about it even knowing you're still on 4.4, that being one of the reasons we don't do as well supporting stuff that old. If it is indeed the same bug, anything even half modern should have it fixed -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman