From owner-freebsd-stable@FreeBSD.ORG Mon Apr 24 20:24:09 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77C2816A402 for ; Mon, 24 Apr 2006 20:24:09 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B20B43D49 for ; Mon, 24 Apr 2006 20:24:08 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k3OKO7vf044650; Tue, 25 Apr 2006 00:24:07 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Tue, 25 Apr 2006 00:24:07 +0400 (MSD) From: Dmitry Morozovsky To: Kris Kennaway In-Reply-To: <20060424181531.GA13774@xor.obsecurity.org> Message-ID: <20060425001751.S44618@woozle.rinet.ru> References: <20060423193208.N1187@woozle.rinet.ru> <20060423201732.GA74905@xor.obsecurity.org> <20060424091803.L20593@woozle.rinet.ru> <20060424215650.P36233@woozle.rinet.ru> <20060424181531.GA13774@xor.obsecurity.org> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Tue, 25 Apr 2006 00:24:07 +0400 (MSD) Cc: stable@freebsd.org Subject: Re: fsck_ufs locked in snaplk 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: Mon, 24 Apr 2006 20:24:09 -0000 On Mon, 24 Apr 2006, Kris Kennaway wrote: KK> > What bothers me most is that it is the only machine reproducibly hangs in KK> > snapshots, and it did not hang before RELENG_5 -> RELENG_6 upgrade. Other KK> > RELENG_6 machines do snapshot backups flawlessly (knock-on-wood!) KK> KK> Are you quite certain it's running up-to-date RELENG_6_1? All known KK> snapshot deadlock issues were believed to have been fixed a few weeks KK> ago. If so, we might need you to enable extra debugging to track this KK> down. Yes, I'm sure it's recent RELENG_6_1: marck@office:/usr/src> cvs stat sys/ufs/ffs/ffs_snapshot.c =================================================================== File: ffs_snapshot.c Status: Up-to-date Working revision: 1.103.2.5 Repository revision: 1.103.2.5 /home/ncvs/src/sys/ufs/ffs/ffs_snapshot.c,v Sticky Tag: RELENG_6_1 (branch: 1.103.2.5.2) Sticky Date: (none) Sticky Options: (none) marck@office:/usr/src> cvs -R up P etc/rc.d/SERVERS P release/doc/en_US.ISO8859-1/errata/article.sgml P release/doc/en_US.ISO8859-1/relnotes/common/new.sgml P release/doc/share/sgml/release.ent P release/doc/zh_CN.GB2312/errata/article.sgml P release/doc/zh_CN.GB2312/relnotes/common/new.sgml P sys/amd64/amd64/identcpu.c P sys/amd64/amd64/initcpu.c P sys/amd64/amd64/pmap.c P sys/amd64/include/md_var.h P sys/amd64/include/specialreg.h P sys/i386/i386/identcpu.c P sys/i386/i386/initcpu.c P sys/i386/include/md_var.h P sys/i386/include/specialreg.h P sys/ia64/ia64/nexus.c (all these changes are non-relevant, are they?) I'll try to build DDB kernel tomorrow evening to check. Which commands should I issue in ddb ? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------