From netch@lucky.net Tue Feb 23 07:21:23 1999
Return-Path: <netch@lucky.net>
Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107])
	by hub.freebsd.org (Postfix) with ESMTP id 2283A11B6A
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 23 Feb 1999 07:21:14 -0800 (PST)
	(envelope-from netch@lucky.net)
Received: (from netch@localhost)
	by burka.carrier.kiev.ua (8.Who.Cares/8.Who.Cares) id RAA05399;
	Tue, 23 Feb 1999 17:21:12 +0200 (EET)
	(envelope-from netch)
Message-Id: <199902231521.RAA05399@burka.carrier.kiev.ua>
Date: Tue, 23 Feb 1999 17:21:12 +0200 (EET)
From: netch@lucky.net
Reply-To: netch@lucky.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: Filesystem stress test crashes FreeBSD 3.1
X-Send-Pr-Version: 3.2

>Number:         10226
>Category:       kern
>Synopsis:       Filesystem stress test crashes FreeBSD 3.1
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 23 07:30:00 PST 1999
>Closed-Date:    Sun May 16 17:23:06 PDT 1999
>Last-Modified:  Sun May 16 17:23:35 PDT 1999
>Originator:     Valentin Nechayev
>Release:        FreeBSD 3.1
>Organization:
Lucky Net Ltd.
>Environment:

FreeBSD 3.1-RELEASE, also 3.1-STABLE cvsup'ed at 18th of February
i386 architecture

>Description:

On running stress test, filesystem activity stops; no file can be opened,
each process which try to open file hangs in 'inode' state (seeing 'top'
command output). No memory activity hangs (i.e., bash can print list of its
variables ('set' command), top redraws its screen every 1-2 seconds);
attempt to run 'ps' command from shell hangs the shell.

The problem seems not to be hardware-related; the same results have been
obtained on different hardware configurations (either IDE or SCSI, Pentium-100
or dual Pentium-II, different motherboards).

Problem repeated after cvsup'ing and building stable system (cvsup'ing
on 18th of February).

This stress test doesn't crash 2.2.8-RELEASE or 3.0-RELEASE.

>How-To-Repeat:

Execute following to create test files:

cat >stress <<\EOF
#!/bin/sh
i=1
while :; do
  nohup sh -c 'find / -type f | xargs fgrep zukabukafoobar' \
	>/dev/null 2>&1 &
  echo $i
  i=`expr $i + 1`
done
EOF
chmod 755 stress

and run it:

./stress

In this configuration, process can create approx. 30 childs before locking.

In another variant:

cat >1 <<\EOF
#!/bin/sh
while :; do
  find / -type f | xargs fgrep zukabukafoobar
done
EOF
cat >2 <<\EOF
#!/bin/sh
nohup ./1 >/dev/null 2>&1 &
EOF
cat >3 <<\EOF
#!/bin/sh
for j in 1 2 3 4 5 6 7 8 9 10; do
  ./2
done
EOF
chmod 755 1 2 3

(to run, type `./3')

normally 3-4 childs (./2) can start before locking.

>Fix:
>Release-Note:
>Audit-Trail:

From: Valentin Nechayev <netch@lucky.net>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: kern/10226: Filesystem stress test crashes FreeBSD 3.1
Date: Fri, 14 May 1999 20:01:58 +0300

 It seems to me that this problem is fixed in current -stable, due to kern/8416
 fixing.
 
 > On running stress test, filesystem activity stops; no file can be opened,
 > each process which try to open file hangs in 'inode' state
 
 --
 NVA
 
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sun May 16 17:23:06 PDT 1999 
State-Changed-Why:  
Fixed along with PR #8416. 
>Unformatted:
