From owner-freebsd-current  Sat Apr  1 05:23:12 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA10622 for current-outgoing; Sat, 1 Apr 1995 05:23:12 -0800
Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA10609 for <current@freebsd.org>; Sat, 1 Apr 1995 05:23:05 -0800
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id FAA19194; Sat, 1 Apr 1995 05:22:53 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id FAA01508; Sat, 1 Apr 1995 05:22:53 -0800
Message-Id: <199504011322.FAA01508@corbin.Root.COM>
X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol
To: Kai.Vorma@hut.fi
cc: current@FreeBSD.org
Subject: Re: panic: update: rofs mod 
In-reply-to: Your message of "Sat, 01 Apr 95 16:05:16 +0300."
             <199504011305.QAA05147@vinkku.hut.fi> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sat, 01 Apr 1995 05:22:52 -0800
Sender: current-owner@FreeBSD.org
Precedence: bulk

># reboot
>syncing disks... done
>fs = /
>panic: update: rofs mod

   There is a check in FFS for attempts to write out dirty buffers on a
read-only filesystem. I was able to get the machine to panic with the above
on reboot by using tunefs on / (I must have incorrectly used the block special
device). I suppose there is a bug somewhere not returning EROFS when writing
to RO-mounted block devices. I seem to recall that prior to 4.4-lite the system
wouldn't let you do anything with a mounted block device.

-DG