Date: Wed, 9 Sep 2009 09:02:33 +0200 From: Mel Flynn <mel.flynn+fbsd.current@mailing.thruhere.net> To: freebsd-current@freebsd.org Cc: Pawel Jakub Dawidek <pjd@freebsd.org>, Jeff Blank <jfb@mr-happy.com> Subject: Re: 8.0-BETA4 panic: ffs_sync: rofs mod Message-ID: <200909090902.34055.mel.flynn%2Bfbsd.current@mailing.thruhere.net> In-Reply-To: <20090909005504.GA12660@mr-happy.com> References: <20090908202553.GA1368@mr-happy.com> <20090908235731.GG1539@garage.freebsd.pl> <20090909005504.GA12660@mr-happy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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] <http://www.freebsd.org/cgi/getmsg.cgi?fetch=407379+0+/usr/local/www/db/text/2009/freebsd-questions/20090823.freebsd-questions>; -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909090902.34055.mel.flynn%2Bfbsd.current>