From owner-freebsd-current Mon Jun 3 2:57:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from web21108.mail.yahoo.com (web21108.mail.yahoo.com [216.136.227.110]) by hub.freebsd.org (Postfix) with SMTP id 16E2E37B400 for ; Mon, 3 Jun 2002 02:57:10 -0700 (PDT) Message-ID: <20020603095709.89835.qmail@web21108.mail.yahoo.com> Received: from [62.254.0.5] by web21108.mail.yahoo.com via HTTP; Mon, 03 Jun 2002 02:57:09 PDT Date: Mon, 3 Jun 2002 02:57:09 -0700 (PDT) From: Hiten Pandya Reply-To: hiten@uk.FreeBSD.org Subject: Re: Deadlock using snapshots To: Peter Jeremy , freebsd-current@freebsd.org In-Reply-To: <20020603111842.D351@gsmx07.alcatel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Peter Jeremy wrote: > I decided to do some experimenting with snapshots and managed to > deadlock my system. (Basically, I had a cron job that was trying > to snapshot all my filesystems every 5 minutes - with a view to > being able to undo any "accidents" I might make). I'd reached > about 5 snapshots per filesystem when it hung. > > I've found a few other anomolies with snapshots, but deadlocks are > undesirable :-(. > > The system was still running normally, but nothing could access the > filesystem. Breaking into 'ps' showed that the deadlocked processes > were all waiting on "inode". I've got a crash dump but would like > some suggestions on where to start looking. > > The system is -CURRENT from 7th May. Is it possible to produce a crash dump? It might provide us with additional information on where it actually deadlocks. Hiten. hiten@uk.FreeBSD.org __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message