From owner-freebsd-geom@FreeBSD.ORG Sat Jan 13 17:56:26 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA7B816A403 for ; Sat, 13 Jan 2007 17:56:26 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30305.mail.mud.yahoo.com (web30305.mail.mud.yahoo.com [209.191.69.67]) by mx1.freebsd.org (Postfix) with SMTP id 84D5A13C428 for ; Sat, 13 Jan 2007 17:56:26 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 51174 invoked by uid 60001); 13 Jan 2007 17:56:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=GerBdZIDbPJeisyIs9bsnGxCYblwxb6Cn0ovBNa8Cm7G2M551p6qwHTEe4mnUp1+MPNsyM02XvljEiP6buWPJXpSle6QISVat2zU9OJM5b8mMe3ckLdi4Bz1MoweQYlV7PwJS3LF4X1b9TJ26u8iaeRStZgnDv6v5r9JPyLcR1I= ; Message-ID: <20070113175625.51172.qmail@web30305.mail.mud.yahoo.com> X-YMail-OSG: PervTLwVM1n.Br3n6kEuMFbHzHjhdJtx_BkJYejXRODcXTGI9yu54EmnC5Bm7wWQLrdF66rd0G3I55ozQrqANkoxVx0z_pDaUb53IgHTTrryPO5ir1DrRHz5uQQBXbWLsBsymmkbW_exz08- Received: from [213.54.176.27] by web30305.mail.mud.yahoo.com via HTTP; Sat, 13 Jan 2007 09:56:25 PST Date: Sat, 13 Jan 2007 09:56:25 -0800 (PST) From: "R. B. Riddick" To: CyberLeo Kitsana In-Reply-To: <45A91A0F.8070701@cyberleo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: FreeBSD Geom Subject: Re: geom_raid5 livelock? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2007 17:56:26 -0000 --- CyberLeo Kitsana wrote: > Good morning! > Thx. U2! :-) > I'm not sure what error 5 is, but it looks ominous. > That is EIO... Dont know where it comes from. We would know better, if u change the line around 1292 or so from G_RAID5_LOGREQ(bp, "[done]"); to G_RAID5_LOGREQ(bp, "[done err%d]",bp->bio_error); and after line 1160 (the line with = EIO;) G_RAID5_LOGREQ(bp, "[not-equal]"); Then wait for this suspected live lock again and look for messages and then set debug level to 2... > The first log shows two seconds of the first test, where only ad2s2 was > showing up. The second log is after a restart of everything, and ad0s2, > ad2s2, and ad6s2 show up, indicating that this most likely isn't just a > drive, bus, or controller failure. > Possibly... Maybe U need to run a verify manually (graid5 configure -R )... Are u sure, that a complete verify run took place after label'ing the graid5 device? > The machine is on a UPS, so power loss isn't too much of an issue. What > other impacts would reducing kern.geom.raid5.wdt have? > OK - UPS is nice... is the number of seconds, graid5 waits before it executes a write request... So lower wdt means, lower chances for write optimization in favor to lower chances for data loss... Btw.: A kernel crash could result in such data loss, too (just like a power failure)... -Arne ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news