Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757255AbZJPIpe (ORCPT ); Fri, 16 Oct 2009 04:45:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752142AbZJPIpd (ORCPT ); Fri, 16 Oct 2009 04:45:33 -0400 Received: from dwdmx5.dwd.de ([141.38.3.242]:35785 "EHLO dwdmx5.dwd.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752135AbZJPIpc (ORCPT ); Fri, 16 Oct 2009 04:45:32 -0400 Date: Fri, 16 Oct 2009 08:44:50 +0000 (GMT) From: Holger Kiehl X-X-Sender: kiehl@praktifix.dwd.de To: Justin Piszcz cc: linux-raid , linux-kernel Subject: Re: Raid reconstructing and process hanging in D state In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 904 Lines: 22 On Fri, 16 Oct 2009, Justin Piszcz wrote: > Hi, > > I have the same problem with mdadm/raid-1, if you do not limit the speed in > the speed_limit_min paramter, it will starve the I/O from all other processes > and result in the same problem you are having. > But in my case speed_limit_min was set to 1000 and speed_limit_max was 200000 (ie. the default) and this still caused all process to hang in D-state. Only lowering speed_limit_max helped to make the system responsive again. > But for me I'm not sure about the reconstruction-- this happens for me during > a raid verify/check. > This was also the case for me, during a raid verify/check. Holger -- 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/