From owner-freebsd-current@FreeBSD.ORG Mon May 25 10:39:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D6331065670; Mon, 25 May 2009 10:39:34 +0000 (UTC) (envelope-from davidn04@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by mx1.freebsd.org (Postfix) with ESMTP id EC8ED8FC12; Mon, 25 May 2009 10:39:33 +0000 (UTC) (envelope-from davidn04@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so1658914qwe.7 for ; Mon, 25 May 2009 03:39:33 -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 :content-transfer-encoding; bh=1zGcmwON1pXK7/3NCK5zcbzhBFdTJVtJU2pev1JICk4=; b=i/XNj1oVCnSxY+xhkOL4gxEPdb03FifnAfp2cEUaLjzPTMoy8eQEVHd8ZroI8NXIZR GhssQ0imnph20jCzMW5Yy8XQGjVJggF1/gIkbL97pai7/Ji2rnCNcmSw/7NfZBVlUNn4 seG6fi173Xk4f38EtyR0FVKelu3afqqjiJOGA= 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:content-transfer-encoding; b=HSBUtgir+9ByQSzNppaYnRtOoB1EiJLLX9i0zLjsO8yC6grG+TOXDIl2/LY83W6aaI xYaMv5ZZdVPsek4/kwVDRGMb2oFosQUqtHznXuBWWI2f6ttPUGDCCB2BVzgs0/ZxWKIF El/JCPxLLiS5u/3Pciu1rkhTrjqUeoGOKS8wE= MIME-Version: 1.0 Received: by 10.229.86.196 with SMTP id t4mr2036154qcl.39.1243247973303; Mon, 25 May 2009 03:39:33 -0700 (PDT) In-Reply-To: References: <4d7dd86f0905250042v61f2af6cl943b665cdbeb26a3@mail.gmail.com> Date: Mon, 25 May 2009 20:39:33 +1000 Message-ID: <4d7dd86f0905250339o6e395102l5074198b38143970@mail.gmail.com> From: David N To: Ivan Voras Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: gjournal locks up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 10:39:34 -0000 2009/5/25 Ivan Voras : > David N wrote: >> Hi, >> >> I've got gjournal on two computers running 7.2-RELEASE (AMD64 and >> i386) both with SATA-I. (150) >> >> GPT + GMirror + GJournal >> >> I've had it soft lock, locking up with no HDD activity. And can't do >> anything, except a hard reset. on both machines. >> >> Box1 (i386) removed a slow HDD and replaced with a faster one, that >> stopped the locking. >> Box2 (AMD64) just happened today whilst test installing zimbra >> (Importing MySQL tables). >> >> Both have 2GB Journals on /usr and 1GB on /var >> >> Has there been any stability patches for GJournal that I can test out? >> or has there been any commited lately? >> >> Or even some tuning that could be done? >> >> If you like i can install a DEBUG Kernel and try to lock it again. >> (Usually heavy disk activity should do it). > > You need to provide more data. How do you know that "gjournal" has > locked up? There is comparatively little in gjournal itself that can > lock up. Is the machine still responsive to network? In what states > (wait channels) are the processes on the machine? > > The network seems okay. The SSH session doesn't close. It just sits there, initiating another SSH just sits there as well, it doesn't time out or anything. I'll compile a debug kernel tonight, and I'll put in the other disk that "should" lock up, tomorrow and copy a few gigs across. The first time it locked up was when i was copying cp -va from one disk (degraded mirrror) to the other disk (degraded mirror + gjournal). Copied around 40GB until it locked up. It did it 3 times before i manage to copy everything over. Re-syncing of the mirror works fine. Should i use options KDB options DDB options INVARIANTS options INVARIANTS_SUPPORT options WITNESS options DIAGNOSTIC ? Regards David N