From owner-freebsd-current@FreeBSD.ORG Tue Sep 14 20:20:27 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id A999D10656C1; Tue, 14 Sep 2010 20:20:27 +0000 (UTC) Date: Tue, 14 Sep 2010 20:20:27 +0000 From: Alexander Best To: Steve Kargl Message-ID: <20100914202027.GA79567@freebsd.org> References: <20100914193922.GA71865@freebsd.org> <20100914200904.GA49806@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100914200904.GA49806@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: Bad cg number with SU+J 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: Tue, 14 Sep 2010 20:20:27 -0000 On Tue Sep 14 10, Steve Kargl wrote: > On Tue, Sep 14, 2010 at 07:39:22PM +0000, Alexander Best wrote: > > hi there, > > > > a few minutes ago my machine froze running HEAD (r212616; amd64). after i did > > a reset i had to deal with a situation i've documented in the attached file. > > > > http://lists.freebsd.org/pipermail/freebsd-current/2010-September/019760.html > > >From an email reply that I received (which was not sent to the > mailing list), it seems that this is a known problem with > SU+J. When you lock up again (which you will), simply > disable journaling. thanks for the info. it seems as if SU+J still as a few rough edges here and there. hope that jeff and kirk will have these sorted out soon. :) cheers. alex > > -- > Steve -- a13x