--- Peter Jeremy <[EMAIL PROTECTED]> 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.
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message