From owner-freebsd-current@FreeBSD.ORG Fri Dec 2 13:42:25 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 E8B6C16A422; Fri, 2 Dec 2005 13:42:24 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB0F243D68; Fri, 2 Dec 2005 13:42:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3007598 for multiple; Fri, 02 Dec 2005 08:40:25 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB2DgHqD002352; Fri, 2 Dec 2005 08:42:20 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 2 Dec 2005 08:40:55 -0500 User-Agent: KMail/1.8.3 References: <20051202103751.T83839@fledge.watson.org> <43904D18.5050503@freebsd.org> In-Reply-To: <43904D18.5050503@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512020840.58395.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: 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 13:42:25 -0000 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: > > > > ad0: 57231MB at ata0-master SATA150 > > acd0: CDRW at ata1-master UDMA= 33 > > Trying to mount root from ufs:/dev/ad0s3a > > WARNING: / was not properly dismounted > > Loading configuration files. > > kernel dumps on /dev/ad0s3b > > Entropy harvesting: interrupts ethernet point_to_point kickstart. > > swapon: adding /dev/ad0s3b as swap device > > Starting file system checks: > > /dev/ad0s3a: INCORRECT BLOCK COUNT I=3D16528 (4 should be 0) (CORRECTED) > > /dev/ad0s3a: UNREF FILE I=3D16528 OWNER=3Droot MODE=3D100444 > > /dev/ad0s3a: SIZE=3D0 MTIME=3DDec 2 10:33 2005 (CLEARED) > > /dev/ad0s3a: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) > > /dev/ad0s3a: SUMMARY INFORMATION BAD (SALVAGED) > > /dev/ad0s3a: BLK(S) MISSING IN BIT MAPS (SALVAGED) > > /dev/ad0s3a: 2378 files, 78670 used, 175145 free (441 frags, 21838 > > blocks, 0.2% > > fragmentation) > > /dev/ad0s3e: DEFER FOR BACKGROUND CHECKING > > /dev/ad0s3d: DEFER FOR BACKGROUND CHECKING > > WARNING: /usr was not properly dismounted > > WARNING: /var was not properly dismounted > > /var: mount pending error: blocks 4 files 1 > > Setting hostname: sesame.cam.watson.org. > > bge0: link state changed to DOWN > > bge0: no link ....bge0: link state changed to UP > > > > ... > > > > /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. > > > > Robert N M Watson > > 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= ,=20 so you might be able to mount -u -w / in single user mode after running fsc= k=20 as a way to recover. Either that or boot single user, run fsck, and then=20 reboot before going into multiuser. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org