From owner-freebsd-stable@FreeBSD.ORG Wed Mar 3 04:14:02 2004 Return-Path: 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 B26DD16A4CE for ; Wed, 3 Mar 2004 04:14:02 -0800 (PST) Received: from shellma.zin.lublin.pl (shellma.zin.lublin.pl [212.182.126.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75BE443D31 for ; Wed, 3 Mar 2004 04:14:02 -0800 (PST) (envelope-from pawmal-posting@freebsd.lublin.pl) Received: by shellma.zin.lublin.pl (Postfix, from userid 1018) id 861B85F103; Wed, 3 Mar 2004 13:14:30 +0100 (CET) Date: Wed, 3 Mar 2004 13:14:30 +0100 From: Pawel Malachowski To: James Read Message-ID: <20040303121430.GB35449@shellma.zin.lublin.pl> References: <20040302213936.216CB5F103@shellma.zin.lublin.pl> <00a501c40171$9e0f6dc0$c000000a@jd2400> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <00a501c40171$9e0f6dc0$c000000a@jd2400> User-Agent: Mutt/1.4.2i cc: stable@freebsd.org Subject: Re: Using read-only NULLFS leads to panic. gdb output included, easy toreproduce. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 12:14:02 -0000 On Wed, Mar 03, 2004 at 10:48:16PM -0000, James Read wrote: > All I can say is that I've had this happen to me before. 'Me too' > > The ports were mounted in exact the same way, but with rw instead of ro. > > Also a few jails were running at the time, infact 3 were. All had /usr/ports > mount_null'ed inside there jail. OT, but it is rather bad idea to have rw mounted /usr/ports shared beetween hosts/jails. Ports tree can be trojaned from one jail and everything can be compromised this way. > After running find from the usual periodic scripts it brought the machine > down every time it ran that script. True, my setup was runnig successfully for months. The only change I made few days ago was to start cron inside jails. :) > If there is a better way / another way to 'mount_null' /usr/ports (or any > other mount point for that matter) to other places in/on the filesystem, by > using NFS or other such things, then speak up! I don't like getting panics > more then anyone else does ;> I hope this can be fixed inside nullfs. Tjr@ asked about reproducing this on 5.x -- it was not possible to panic, so a fix may be already in HEAD. However, second problem (every process stalls after trying do play with filesystem) was exposed, see other posts in this thread. -- Paweł Małachowski