Date: Mon, 3 Jun 2002 02:57:09 -0700 (PDT) From: Hiten Pandya <hitmaster2k@yahoo.com> To: Peter Jeremy <peter.jeremy@alcatel.com.au>, freebsd-current@freebsd.org Subject: Re: Deadlock using snapshots Message-ID: <20020603095709.89835.qmail@web21108.mail.yahoo.com> In-Reply-To: <20020603111842.D351@gsmx07.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Peter Jeremy <peter.jeremy@alcatel.com.au> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020603095709.89835.qmail>