From owner-freebsd-current@FreeBSD.ORG Fri Dec 2 17:03:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 95C5016A424 for ; Fri, 2 Dec 2005 17:03:03 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C73643D64 for ; Fri, 2 Dec 2005 17:02:53 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EiEFh-0001kX-C3 for freebsd-current@freebsd.org; Fri, 02 Dec 2005 17:59:17 +0100 Received: from gw205.f5.com ([205.229.151.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 02 Dec 2005 17:59:17 +0100 Received: from atkin901 by gw205.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 02 Dec 2005 17:59:17 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Fri, 02 Dec 2005 08:55:02 -0800 Lines: 36 Message-ID: References: <20051202103751.T83839@fledge.watson.org> <43904D18.5050503@freebsd.org> <200512020840.58395.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gw205.f5.com User-Agent: KNode/0.9.3 Sender: news Subject: Re: After crash, / comes up mounted read-only, but in multiuser; mfs /tmp? 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: Fri, 02 Dec 2005 17:03:03 -0000 John Baldwin wrote: > On Friday 02 December 2005 08:33 am, David Xu wrote: >> Robert Watson wrote: > I've seen reports that mount -u -w / works whereas mount -u -o rw / > doesn't, so you might be able to mount -u -w / in single user mode after > running fsck > as a way to recover. Either that or boot single user, run fsck, and then > reboot before going into multiuser. Yep, that's what I found. mount -o rw no longer works only -w. Interestingly '-o rw' is not in the manpage, which is how I originally discovered that '-w' was working. One script in rc.d appears to use it. However I think it would be better to fix the mount options they way they were. I noticed also that if you go multi-user after a crash, you'll get the mfs mounts noted above and in addition the only way to mount / is to reboot. Dropping to single user and attempting to mount -w after the fsck completes complains about invalid argument or invalid device /dev/ad0s1a. --- etc/rc.d/root.org Fri Dec 2 08:48:15 2005 +++ etc/rc.d/root Fri Dec 2 08:48:29 2005 @@ -23,7 +23,7 @@ [Nn][Oo] | '') ;; *) - if ! mount -u -o rw /; then + if ! mount -u -w /; then echo 'Mounting root filesystem rw failed, startup aborted' /bin/kill -QUIT $$ --- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired);