From ishizuka@ish.org  Sat Sep  2 22:57:41 2000
Return-Path: <ishizuka@ish.org>
Received: from onion.ish.org (onion.ish.org [210.145.219.202])
	by hub.freebsd.org (Postfix) with ESMTP id A98A837B422
	for <FreeBSD-gnats-submit@freebsd.org>; Sat,  2 Sep 2000 22:57:40 -0700 (PDT)
Received: (from ishizuka@localhost)
	by onion.ish.org (8.9.3/3.7Wpl2-2000/05/28) id OAA97636;
	Sun, 3 Sep 2000 14:57:39 +0900 (JST)
Message-Id: <200009030557.OAA97636@onion.ish.org>
Date: Sun, 3 Sep 2000 14:57:39 +0900 (JST)
From: Masachika ISHIZUKA <ishizuka@ish.org>
Reply-To: ishizuka@ish.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: /etc/security make the system hangup
X-Send-Pr-Version: 3.2

>Number:         21009
>Category:       kern
>Synopsis:       /etc/security make the system hangup
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Sep 02 23:00:01 PDT 2000
>Closed-Date:    Mon Mar 12 20:04:34 PST 2001
>Last-Modified:  Mon Mar 12 20:04:48 PST 2001
>Originator:     Masachika ISHIZUKA
>Release:        FreeBSD 4.1-RELEASE i386
>Organization:
>Environment:

	Too many files on disks.

>Description:

	daily cron crashs system if I have too many files
	on disks as follows.

	/etc/crontab (periodic daily)
	-> /etc/periodic/daily/450.status-security
	-> /etc/security

>How-To-Repeat:

	

>Fix:

	I don't know.
	I have too many files on the disk mounted to /www,
	I changed line 30 of /etc/security from

	MP=`mount -t ufs | grep -v " nosuid" | sed 's;/dev/;&r;'
	     | awk '{ print $3 }'`

	to

	MP=`mount -t ufs | grep -v " nosuid" | sed 's;/dev/;&r;'
	     | awk '{ print $3 }' | grep -v '^/www$'`

	But it is not good idea, I think.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Mon Sep 4 06:32:11 PDT 2000 
State-Changed-Why:  
Please explain what "crashs system" means.  Since the environment 
you describe is hard to set up (especially given that you don't 
define "too many files"), this will be easier to investigate 
based on the actual error messages you see. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21009 

From: Masachika ISHIZUKA <ishizuka@ish.org>
To: sheldonh@freebsd.org
Cc: freebsd-bugs@freebsd.org
Subject: Re: kern/21009: /etc/security make the system hangup
Date: Wed, 06 Sep 2000 18:45:56 +0900

 > Synopsis: /etc/security make the system hangup
 > State-Changed-From-To: open->feedback
 > State-Changed-By: sheldonh
 > State-Changed-When: Mon Sep 4 06:32:11 PDT 2000
 > State-Changed-Why: 
 >
 > Please explain what "crashs system" means.  Since the environment
 > you describe is hard to set up (especially given that you don't
 > define "too many files"), this will be easier to investigate
 > based on the actual error messages you see.
 > 
 > http://www.freebsd.org/cgi/query-pr.cgi?pr=21009
 
   Hi, sheldonh-san.
   Thank you for your mail.
 There is no error messages. I can't login if it happens. There is
 no response from ping.
   Only Alt-F? is available, but after screen is switched by Alt-F?,
 I push return key and the login prompt will be scrolled up with no
 news messages. After I typed return key for 25 times, there is no
 messages on screen at all.
 
   There are 4 machines with hangup. The following is the output of
 'df -ki' command. All machines are 4.1-RELEASE. Most of directories
 and files on the disk mounted on /www have about 5000 hard links,
 so there are more than 6,000,000 links, files or directories on each
 /www disks.
   The running time for /etc/security is about 1.5 or 2.5 hours on
 Pentium III/600 or Pentium II/400.  The ccd0c and /dev/vinum/www
 are two 16GB or 20GB UDMA33 ata drives with striped.
 
 (1)
 /dev/ccd0c   17591175  1999479 14184402    12%  443610 3952932    10%   /www
 
 (2)
 /dev/ccd0c   17072631  2645276 13061545    17%  448429 8096465     5%   /www
 
 (3)
 /dev/vinum/www  17072515   353165 15353549     2%  119432 8425462     1%   /www
 
 (4)
 /dev/ccd0c   17072631  2407959 13298862    15%  454757 8090137     5%   /www
 
 -- 
 ishizuka@ish.org
 
 

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Masachika ISHIZUKA <ishizuka@ish.org>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/21009: /etc/security make the system hangup 
Date: Wed, 06 Sep 2000 13:15:33 +0200

 On Wed, 06 Sep 2000 02:50:04 MST, Masachika ISHIZUKA wrote:
 
 >    There are 4 machines with hangup. The following is the output of
 >  'df -ki' command. All machines are 4.1-RELEASE. Most of directories
 >  and files on the disk mounted on /www have about 5000 hard links,
 >  so there are more than 6,000,000 links, files or directories on each
 >  /www disks.
 >    The running time for /etc/security is about 1.5 or 2.5 hours on
 >  Pentium III/600 or Pentium II/400.  The ccd0c and /dev/vinum/www
 >  are two 16GB or 20GB UDMA33 ata drives with striped.
 
 Could you stick a debugging kernel on one of those boxes and use DDB or
 remote kgdb to figure out what the kernel's stuck in?  There are just
 two many variables here.
 
 Instructions that you might find helpful are available at:
 
 	http://www.freebsd.org/handbook/kerneldebug.html
 
 Ciao,
 Sheldon.
 

From: Masachika ISHIZUKA <ishizuka@ish.org>
To: sheldonh@uunet.co.za
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/21009: /etc/security make the system hangup 
Date: Thu, 07 Sep 2000 01:13:49 +0900

 >>    There are 4 machines with hangup. The following is the output of
 >>  'df -ki' command. All machines are 4.1-RELEASE. Most of directories
 >>  and files on the disk mounted on /www have about 5000 hard links,
 >>  so there are more than 6,000,000 links, files or directories on each
 >>  /www disks.
 > 
 > Could you stick a debugging kernel on one of those boxes and use DDB or
 > remote kgdb to figure out what the kernel's stuck in?  There are just
 > two many variables here.
 >
 > Instructions that you might find helpful are available at:
 > 
 > 	http://www.freebsd.org/handbook/kerneldebug.html
 
   Hi, sheldonh-san.
   Thank you for mail.
 I'll try above. But these machines are not able to panic, so I
 must create a test machine with the same environment. Because
 I'm too busy to do so, please wait for a couple of weeks or more.
 
 -- 
 ishizuka@ish.org
 

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Masachika ISHIZUKA <ishizuka@ish.org>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/21009: /etc/security make the system hangup 
Date: Wed, 06 Sep 2000 18:53:31 +0200

 On Thu, 07 Sep 2000 01:15:20 +0900, Masachika ISHIZUKA wrote:
 
 > I'll try above. But these machines are not able to panic, so I
 > must create a test machine with the same environment. Because
 > I'm too busy to do so, please wait for a couple of weeks or more.
 
 Another suggestion that I got in private mail was this:
 
 Run something like this on its own virtual terminal:
 
 	while sleep 1; do
 		vmstat -m | tail -2
 	done
 
 Report back the values displayed at the time of the lock-up.  This
 should be easy to do, since you said that you were able to switch
 virtual terminals during the lock-up.
 
 Ciao,
 Sheldon.
 
State-Changed-From-To: feedback->closed 
State-Changed-By: des 
State-Changed-When: Mon Mar 12 20:04:34 PST 2001 
State-Changed-Why:  
Feedback timeout. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21009 
>Unformatted:
