From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 18:18:07 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC9461065697 for ; Thu, 10 Sep 2009 18:18:07 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 471358FC08 for ; Thu, 10 Sep 2009 18:18:06 +0000 (UTC) Received: by bwz2 with SMTP id 2so279591bwz.43 for ; Thu, 10 Sep 2009 11:18:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=hcqluhMizU+7qQ20+ryutNkl0ZM0VqdO51jcZOvnZ1s=; b=jnysrDUxR5Hp/Czob5O/xOuz/8W7Pzs9r7INGSji8ShQCOeJUmlKFhUbZwHbusj2/+ IiZ4tN96fwU0aWUwmPGm+H69BcurVtguCqCOX+wYgpcdqPXTCVPXFiVnIZtnf/68vniJ y6PbodhBQJqNLeWQ24L1xr27j8fTmbcR+plSc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=sJ/chcyveJlY2W50VzFu2S93Ixtsgeny1cd/+wqAGUN7lXQNhvuXLoSlduOj4eioyO Q+AgRA5CS7r+CZ2szkplCiuDoSCvoedQAn39zwPZjT9EeTQwBToIVgfIeWdmGRd1RPAU CjS79n68qkdl7jB9UpdSPSiknS84bN/2CwUxI= MIME-Version: 1.0 Received: by 10.204.19.145 with SMTP id a17mr1194024bkb.64.1252606686018; Thu, 10 Sep 2009 11:18:06 -0700 (PDT) In-Reply-To: <4AA92EF1.6010804@eng.auth.gr> References: <4AA90D88.4010004@eng.auth.gr> <4AA92EF1.6010804@eng.auth.gr> Date: Thu, 10 Sep 2009 22:18:05 +0400 Message-ID: From: pluknet To: George Mamalakis Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2009 18:18:08 -0000 2009/9/10 George Mamalakis : [about aac0: COMMAND 0xffffff80003d9440 TIMEOUT AFTER 40 SECONDS] >> It looks like the controller was too busy rebuilding to take any new >> requests. It is possible you have filled the controller's write cache and >> that is why the lag happened at this point. You can easily test this theory. >> > This is the exact reason why I am asking this question. If this behavior is > normal, then there is no problem with me. But I couldn't be sure whether it > was a driver's problem or a controller's problem. > I see it from time to time on a number of boxes. You can often ignore this. It might be due to (and a symptom of) high disk workload. Btw, there was a recent change to increase command timeout to 120s. > Thank you for your answer again, and (now that you mentioned it:) ) in case > anyone knows whether we'll be able to see partitions > 2T in the future (or > now?!), please say how :). > Look at gpart(8). -- wbr, pluknet