From owner-freebsd-current@FreeBSD.ORG Wed Sep 9 07:02:37 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F20B1065679; Wed, 9 Sep 2009 07:02:37 +0000 (UTC) (envelope-from mel.flynn+fbsd.current@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 4E5128FC0A; Wed, 9 Sep 2009 07:02:36 +0000 (UTC) Received: from smoochies.rachie.is-a-geek.net (mailhub.lan.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id AFE747E818; Tue, 8 Sep 2009 23:02:48 -0800 (AKDT) From: Mel Flynn To: freebsd-current@freebsd.org Date: Wed, 9 Sep 2009 09:02:33 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-BETA4; KDE/4.2.4; i386; ; ) References: <20090908202553.GA1368@mr-happy.com> <20090908235731.GG1539@garage.freebsd.pl> <20090909005504.GA12660@mr-happy.com> In-Reply-To: <20090909005504.GA12660@mr-happy.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909090902.34055.mel.flynn+fbsd.current@mailing.thruhere.net> Cc: Pawel Jakub Dawidek , Jeff Blank Subject: Re: 8.0-BETA4 panic: ffs_sync: rofs mod X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 09 Sep 2009 07:02:37 -0000 On Wednesday 09 September 2009 02:55:04 Jeff Blank wrote: > On Wed, Sep 09, 2009 at 01:57:31AM +0200, Pawel Jakub Dawidek wrote: > > On Tue, Sep 08, 2009 at 04:25:53PM -0400, Jeff Blank wrote: > > > Please let me know if I need to provide more details. > > > > [...] > > > > > fs = /old > > > panic: ffs_sync: rofs mod > > > > I have no idea why UFS thinks file system is read-only. > > hmm, I do have it marked as read-only in /etc/fstab, but I'd been > mounting it with '-o rw'. This problem has also been seen on -questions [1] and I forgot to follow up after time issues. According to the poster it's easy to reproduce: - have a mountpoint in /etc/fstab with ro options - unmount the mountpoint - remount using -o rw The behavior does not occur if one uses mount -u -o rw without unmounting. I think this is a too easy way to panic the kernel. [1] -- Mel