Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 15 Oct 2001 23:43:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 15 Oct 2001 23:43:34 -0400 Received: from tone.orchestra.cse.unsw.EDU.AU ([129.94.242.28]:3529 "HELO tone.orchestra.cse.unsw.EDU.AU") by vger.kernel.org with SMTP id ; Mon, 15 Oct 2001 23:43:19 -0400 From: Neil Brown To: "Jeffrey W. Baker" Date: Tue, 16 Oct 2001 13:43:40 +1000 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15307.44268.700557.852375@notabene.cse.unsw.edu.au> cc: Subject: Re: very slow RAID-1 resync In-Reply-To: message from Jeffrey W. Baker on Monday October 15 In-Reply-To: X-Mailer: VM 6.72 under Emacs 20.7.2 X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D I just plugged in a new RAID-1(+0, 2 2-disk stripe sets mirrored) to a > 2.4.12-ac3 machine. The md code decided it was going to resync the mirror > at between 100KB/sec and 100000KB/sec. The actual rate was 100KB/sec, > while the device was otherwise idle. By increasing > /proc/.../speed_limit_min, I was able to crank the resync rate up to > 20MB/sec, which is slightly more reasonable but still short of the > ~60MB/sec this RAID is capable of. > > So, two things: there is something wrong with the resync code that makes > it run at the minimum rate even when the device is idle, and why is the > resync proceeding so slowly? The way that it works out where there is other activity on the drives is a bit fragile. It works particularly badly when the underlying devices are md devices. I would recommend that instead of mirroring 2 stipe sets, you stripe two mirrored pairs. The resync should be faster and the resilience to failure is much better. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/