From owner-freebsd-stable@FreeBSD.ORG  Wed Mar  3 03:09:04 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
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)
Date: Wed, 3 Mar 2004 12:09:30 +0100
From: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl>
To: Tim Robbins <tjr@freebsd.org>
Message-ID: <20040303110930.GA35449@shellma.zin.lublin.pl>
References: <20040302213936.216CB5F103@shellma.zin.lublin.pl>
	<20040303002536.GA59500@cat.robbins.dropbear.id.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20040303002536.GA59500@cat.robbins.dropbear.id.au>
User-Agent: Mutt/1.4.2i
cc: stable@freebsd.org
cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: Using read-only NULLFS leads to panic. gdb output included,
	easy to reproduce.
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2004 11:09:04 -0000

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ł Małachowski