Date: Mon, 22 Feb 1999 22:43:12 -0500 (EST) From: Brian Feldman <green@unixhelp.org> To: "Alexander N. Kabaev" <kan@sti.cz> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Filesystem deadlock Message-ID: <Pine.BSF.4.05.9902222238440.1759-100000@janus.syracuse.net> In-Reply-To: <36D1898A.6D9C7B44@sti.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Feb 1999, Alexander N. Kabaev wrote: > The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE > as of today) to lookup. Shortly after this script is started, all disk activity > > stops and any attempt to create new process causes system to freese. While in DDB, ps command > > shows, that all ten fgrep processes are sleeping on inode, all xargs are in waitpid and > > all sh processes are in wait. You forget about all the processes (just a few, actually) stuck in "kmaw" (kmem_alloc_wait). This is definitely reproducible :( Should be simple for someone more knowledgeable to diagnose, as it looks to be a straight vm/vfs(ufs/ffs) interaction. > > Unfortunately, I cannot run -g kernel on my box > at this time, so amount of useful information I can provide is pretty much > limited :( > > #!/bin/sh > for j in 1 2 3 4 5 6 7 8 9 10; do > echo -n $i $j > nohup sh -c 'while :; do find /usr -type f | xargs fgrep zukabuka; > done' \ > >/dev/null 2>&1 & > echo > done > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ 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?Pine.BSF.4.05.9902222238440.1759-100000>