From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 12:10:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 966C216A4CE for ; Sun, 7 Nov 2004 12:10:45 +0000 (GMT) Received: from email11.aon.at (warsl404pip7.highway.telekom.at [195.3.96.91]) by mx1.FreeBSD.org (Postfix) with SMTP id 9C79943D41 for ; Sun, 7 Nov 2004 12:10:44 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail 128062 invoked from network); 7 Nov 2004 12:10:42 -0000 Received: from m082p009.dipool.highway.telekom.at (HELO ?62.46.0.41?) ([62.46.0.41]) (envelope-sender ) by email11.aon.at (qmail-ldap-1.03) with SMTP for ; 7 Nov 2004 12:10:42 -0000 From: Stefan Ehmann To: Poul-Henning Kamp In-Reply-To: <6387.1099765504@critter.freebsd.dk> References: <6387.1099765504@critter.freebsd.dk> Content-Type: text/plain Message-Id: <1099829438.890.11.camel@taxman> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 07 Nov 2004 13:10:38 +0100 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: ext2fs related panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 12:10:45 -0000 On Sat, 2004-11-06 at 19:25, Poul-Henning Kamp wrote: > Ok, can you try the stuff in current, I've made two commits > and you want both. Thanks, these fix the previous panics reported by me. I was able to produce yet another panic: mount /mnt/stuff mount -u -o rw /mnt/stuff touch /mnt/stuff/foo mount -u -o ro /mnt/stuff umount /mnt/stuff At this point I get this: g_vfs_done():ad1s1[WRITE(offset=4096, length=4096)]error = 1 g_vfs_done():ad1s1[WRITE(offset=8192, length=4096)]error = 1 g_vfs_done():ad1s1[WRITE(offset=20480, length=4096)]error = 1 g_vfs_done():ad1s1[WRITE(offset=27380416512, length=4096)]error = 1 A few seconds later I get this: Fatal trap 12: page fault while in kernel mode current process = 55 (syncer) trace g_io_request() bufwrite() vop_stdfsync() sched_sync() fork_exit() fork_trampoline() If I do not use mount -u but simply unmount and mount rw afterwards there seems to be no problem. (So this is not that critcal for me) > In message <1099751434.868.1.camel@taxman>, Stefan Ehmann writes: > >On Sat, 2004-11-06 at 14:43, Poul-Henning Kamp wrote: > >> Ok, then try this patch: > >Still causing the same panic here. > >