From owner-freebsd-current@FreeBSD.ORG Fri Dec 2 13:33:18 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 15ACF16A41F; Fri, 2 Dec 2005 13:33:16 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43904D18.5050503@freebsd.org> Date: Fri, 02 Dec 2005 21:33:12 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.11) Gecko/20050911 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <20051202103751.T83839@fledge.watson.org> In-Reply-To: <20051202103751.T83839@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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:33:18 -0000 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 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 > I have seen this for some days, one machine I even have to reinstall the system because mount -u / does not work. :-( David Xu