From owner-freebsd-current Sun Jun 2 18:18:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail2.alcanet.com.au [203.62.196.17]) by hub.freebsd.org (Postfix) with ESMTP id B777837B403 for ; Sun, 2 Jun 2002 18:18:47 -0700 (PDT) Received: from mfg1.cim.alcatel.com.au (localhost.localdomain [127.0.0.1]) by alcanet.com.au (8.12.1/8.12.1/Alcanet1.2) with ESMTP id g531IjaQ000941 for ; Mon, 3 Jun 2002 11:18:45 +1000 Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01KIHQ7URMWG8XAEE4@cim.alcatel.com.au> for freebsd-current@freebsd.org; Mon, 3 Jun 2002 11:18:44 +1000 Received: from gsmx07.alcatel.com.au (localhost [127.0.0.1]) by gsmx07.alcatel.com.au (8.12.3/8.12.3) with ESMTP id g531IhbK001136 for ; Mon, 03 Jun 2002 11:18:43 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.12.3/8.12.3/Submit) id g531Igdf001135 for freebsd-current@freebsd.org; Mon, 03 Jun 2002 11:18:42 +1000 (EST) Content-return: prohibited Date: Mon, 03 Jun 2002 11:18:42 +1000 From: Peter Jeremy Subject: Deadlock using snapshots To: freebsd-current@freebsd.org Mail-Followup-To: freebsd-current@freebsd.org Message-id: <20020603111842.D351@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5.1i X-Authentication-warning: gsmx07.alcatel.com.au: jeremyp set sender to peter.jeremy@alcatel.com.au using -f 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 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. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message