From owner-freebsd-current@FreeBSD.ORG Fri Dec 2 10:42:03 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 3E03D16A420 for ; Fri, 2 Dec 2005 10:42:03 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAC6543D45 for ; Fri, 2 Dec 2005 10:42:02 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id D495B46C11 for ; Fri, 2 Dec 2005 05:41:59 -0500 (EST) Date: Fri, 2 Dec 2005 10:41:59 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: <20051202103751.T83839@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: 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 10:42:03 -0000 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 UDMA33 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=16528 (4 should be 0) (CORRECTED) /dev/ad0s3a: UNREF FILE I=16528 OWNER=root MODE=100444 /dev/ad0s3a: SIZE=0 MTIME=Dec 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