Date: Fri, 7 May 1999 09:49:36 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Kevin Day <toasty@home.dragondata.com> Cc: current@FreeBSD.ORG Subject: Re: -current deadlocks within 5 mins, over NFS Message-ID: <199905071649.JAA45656@apollo.backplane.com> References: <199905070817.DAA15632@home.dragondata.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:Matt, I told you about this before, but completely forgot about it. After
:doing considerable testing on my test servers, i thought -current was safe
:enough to try on our production shell servers. I installed -current on one
:of my servers, and to my dismay, it hung. :)
:
:Within 5 minutes of running, nearly every process is blocked on 'inode',
:with the exception of a single 'cp' stuck in vmopar.
:
:I have a very silly, *very* poorly written script i run out of cron, every
:10 mins or so, to update my passwd and group files.
:
:#/bin/sh
:...
:
:What more info do you need for help in debugging this?
:
:Kevin
This is great! Just what I've been looking for! I'll try to reproduce
the lockup today. If it is stuck in vmopar I already have a good idea
about what is going on.
-Matt
Matthew Dillon
<dillon@backplane.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?199905071649.JAA45656>