From owner-freebsd-current@FreeBSD.ORG Fri Dec 2 16:09:36 2005 Return-Path: X-Original-To: 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 7D96D16A41F; Fri, 2 Dec 2005 16:09:36 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id A48C343D76; Fri, 2 Dec 2005 16:09:27 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051202160926.UUTM1186.mta10.adelphia.net@[192.168.1.254]>; Fri, 2 Dec 2005 11:09:26 -0500 Message-ID: <439071AF.2050301@savvis.net> Date: Fri, 02 Dec 2005 08:09:19 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20051202103751.T83839@fledge.watson.org> <43904D18.5050503@freebsd.org> <200512020840.58395.jhb@freebsd.org> In-Reply-To: <200512020840.58395.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Robert Watson , David Xu , 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 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 16:09:36 -0000 John Baldwin wrote: > On Friday 02 December 2005 08:33 am, David Xu wrote: > >>Robert Watson wrote: >> >>>While testing the new DRM update (went badly :-), I crashed my system >>>and had to power cycle it. When it came back up, not surprisingly, >>>the file systems weren't clean. When I reached a login prompt, I >>>logged in to modify /etc/rc.conf, and to my surprise, was told that >>>/etc/rc.conf wasn't writable. Turns out it was because / was mounted >>>read-only: >>> >>>... >>> >>>/dev/ad0s3a on / (ufs, local, read-only) >>>devfs on /dev (devfs, local) >>>/dev/ad0s3e on /usr (ufs, local, soft-updates) >>>/dev/ad0s3d on /var (ufs, local, soft-updates) >>>/dev/md0 on /tmp (ufs, local) >>> >>>The rc scripts helpfully mounted an MFS /tmp for me, which while >>>friendly, succeeded in masking the problem and allowing the system to >>>come up in a rather undesirable state (from my perspective). So it >>>sounds like maybe / wasn't remounted properly, and then the scripts >>>were too helpful thinking it was a diskless system. >>> >> >>I have seen this for some days, one machine I even have to reinstall >>the system because mount -u / does not work. :-( > > 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. this is all very nice as workaround, but does somebody actually working on the _real_ problem? it would be nice to have something in UPDATING saying this is broken now. all i can find in UPDATING is 20051129: The nodev mount option was deprecated in RELENG_6 (where it was a no-op), and is now unsupported. If you have nodev or dev listed in /etc/fstab, remove it, otherwise it will result in a mount error. sure that is not the problem, is it? thanks, max