From pawmal-posting@freebsd.lublin.pl  Wed Mar  3 03:09:04 2004
Return-Path: <pawmal-posting@freebsd.lublin.pl>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 04ACB16A4CE; Wed,  3 Mar 2004 03:09:04 -0800 (PST)
Received: from shellma.zin.lublin.pl (shellma.zin.lublin.pl [212.182.126.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B601943D3F; Wed,  3 Mar 2004 03:09:03 -0800 (PST)
	(envelope-from pawmal-posting@freebsd.lublin.pl)
Received: by shellma.zin.lublin.pl (Postfix, from userid 1018)
	id E66475F103; Wed,  3 Mar 2004 12:09:30 +0100 (CET)
Message-Id: <20040303110930.GA35449@shellma.zin.lublin.pl>
Date: Wed, 3 Mar 2004 12:09:30 +0100
From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl>
To: Tim Robbins <tjr@freebsd.org>
Cc: FreeBSD-gnats-submit@freebsd.org, stable@freebsd.org
In-Reply-To: <20040303002536.GA59500@cat.robbins.dropbear.id.au>
Subject: Re: Using read-only NULLFS leads to panic. gdb output included, easy to reproduce.
References: <20040302213936.216CB5F103@shellma.zin.lublin.pl> <20040303002536.GA59500@cat.robbins.dropbear.id.au>

>Number:         63684
>Category:       kern
>Synopsis:       Re: Using read-only NULLFS leads to panic. gdb output included, easy to reproduce.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Mar 03 03:10:20 PST 2004
>Closed-Date:    Thu Apr 01 10:48:46 PST 2004
>Last-Modified:  Thu Apr 01 10:48:46 PST 2004
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 On Wed, Mar 03, 2004 at 11:25:36AM +1100, Tim Robbins wrote:
 
 > There are known bugs in nullfs in all 4.x releases to date, and in 5.0.
 > If I have time, I may MFC the fixes some time before 4.10 is released.
 
 Sounds interesting.
 
 > Can you reproduce these problems on 5.1 or 5.2?
 
 Procedure:
 mount_null -o ro /usr/ports /mnt/1
 find /usr/ports -type f -perm -u+s &
 find /mnt/1 -type f -perm -u+s &
 ...
 <about 30-40 processess of find(1) was enough>
 
 
 I was not able to reproduce panic on 5.1-RELEASE system.
 
 However, I've reproduced second problem described in this PR,
 which happened to me on 4.9-STABLE once.
 *Every* time (I've tried four times) 5.1-RELEASE becomes unusable
 and non-rebootable, all find(1) processes stuck into 'ufs' state,
 CPU is 100% idle, no disk activity, other processess, when trying
 to read from filesystem, become frozen. I'm able to switch beetween
 consoles and to observe top(1) (started earlier). Ctrl+Alt+Del
 does not work.
 
 One mount_null is sufficient, but more than one null mount seems
 (or it was an accident) to decrease the time we have to wait.
 
 
 -- 
 Pawe Maachowski
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Thu Apr 1 10:48:15 PST 2004 
State-Changed-Why:  
Misfiled followup to kern/63662; text has been copied over. 


Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Apr 1 10:48:15 PST 2004 
Responsible-Changed-Why:  

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