Ollivier Robert wrote:
> According to Kris Kennaway:
> > load: 0.00 cmd: tcsh 8403 [inode] 0.01u 0.00s 0% 1076k
>
> The dreaded "inode" problem. I've been seeing this from time to time where the
> system will be blocked for all I/O on a given disk with all processes waiting
> on "inode".
>
> Ge
According to Kris Kennaway:
> load: 0.00 cmd: tcsh 8403 [inode] 0.01u 0.00s 0% 1076k
The dreaded "inode" problem. I've been seeing this from time to time where the
system will be blocked for all I/O on a given disk with all processes waiting
on "inode".
Generally updating the system to a more r
On Sun, Oct 13, 2002 at 12:12:43AM -0400, Jeff Roberson wrote:
> Can you back out my scheduler changes just to be sure? I can not foresee
> any way that they could cause this, but I'd like to be certain. Blocking
> on inode usually indicates a vfs deadlock. Can you break into ddb and
> type 'sh
On Sat, 12 Oct 2002, Kris Kennaway wrote:
> I'm having a strange problem with my -current box: I am running the
> bfbtester port on system utilities, which basically forks 100 copies
> of the binary at once to test different options. The problem is that
> sometimes the -current system becomes una
On Sun, Oct 13, 2002 at 12:12:43AM -0400, Jeff Roberson wrote:
> Can you back out my scheduler changes just to be sure?
I don't think I'm running them:
FreeBSD 5.0-CURRENT (ROT13) #1: Fri Oct 11 01:14:18 PDT 2002
> I can not foresee
> any way that they could cause this, but I'd like to be certa
I'm having a strange problem with my -current box: I am running the
bfbtester port on system utilities, which basically forks 100 copies
of the binary at once to test different options. The problem is that
sometimes the -current system becomes unable to fork *any* new
processes, and even suspendin
