From owner-freebsd-current@FreeBSD.ORG Fri Dec 2 21:06:05 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 63CEE16A41F for ; Fri, 2 Dec 2005 21:06:05 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id C113D43D5A for ; Fri, 2 Dec 2005 21:05:56 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jB2L5tfO050201; Fri, 2 Dec 2005 13:05:55 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jB2L5t43050200; Fri, 2 Dec 2005 13:05:55 -0800 (PST) (envelope-from jmg) Date: Fri, 2 Dec 2005 13:05:54 -0800 From: John-Mark Gurney To: othermark Message-ID: <20051202210554.GW885@funkthat.com> Mail-Followup-To: othermark , freebsd-current@freebsd.org 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-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-current@freebsd.org 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 Reply-To: John-Mark Gurney 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 21:06:05 -0000 othermark wrote this message on Fri, Dec 02, 2005 at 08:55 -0800: > 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. If we do this, then we should require people to remove the rw option from their fstab file: grep rw /etc/fstab /dev/ar0s1a / ufs rw 1 1 /dev/ar0s1e /usr ufs rw 2 2 /dev/ar0s1d /var ufs rw 2 2 /dev/ar1e /a ufs rw 1 2 /dev/ar0s1f /d ufs rw,nosuid 2 2 #/dev/ad0s1g /g ufs rw,nosuid 1 2 proc /proc procfs rw 0 0 Otherwise, that won't/shouldn't work... since the rw line is the options passed to -o... which is probably why some of us use it w/o thinking.. :) Though it looks like there is a patch that addresses this issue... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."