From owner-freebsd-questions@FreeBSD.ORG Mon Nov 5 18:16:14 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C90016A469 for ; Mon, 5 Nov 2007 18:16:14 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 8EB0E13C4B5 for ; Mon, 5 Nov 2007 18:16:13 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from doc.sem.ipt.ru ([192.168.12.1] helo=srv.sem.ipt.ru) by services.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1Ip6AE-000GQJ-H1; Mon, 05 Nov 2007 20:55:06 +0300 To: Christopher Key References: <472F4C16.5020406@cam.ac.uk> From: Boris Samorodov Date: Mon, 05 Nov 2007 20:57:47 +0300 In-Reply-To: <472F4C16.5020406@cam.ac.uk> (Christopher Key's message of "Mon\, 05 Nov 2007 17\:00\:06 +0000") Message-ID: <99846340@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.99 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: questions@freebsd.org Subject: Re: fsck and memory filesytems (fsck_mfs: No such file or directory) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2007 18:16:14 -0000 On Mon, 05 Nov 2007 17:00:06 +0000 Christopher Key wrote: > I recently had a powercut to my FreeBSD home server, and I'm now > getting the following messages at startup: > Starting file system checks: > /dev/ad8s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad8s1a: clean, 466797 free (2837 frags, 57995 blocks, 0.6% > fragmentation) > fsck: exec fsck_mfs for md in /sbin:/usr/sbin: No such file or directory > fsck: exec fsck_mfs for md in /sbin:/usr/sbin: No such file or directory > /dev/ad8s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad8s1f: clean, 214294022 free (173430 frags, 26765074 blocks, > 0.1% fragmentation) > /dev/mirror/gm0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mirror/gm0s1d: clean, 16121593 free (1441 frags, 2015019 blocks, > 0.0% fragmentation) > /dev/mirror/gm0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mirror/gm0s2d: clean, 63140067 free (4187 frags, 7891985 blocks, > 0.0% fragmentation) > /dev/ad8s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad8s1e: clean, 8049657 free (1169 frags, 1006061 blocks, 0.0% > fragmentation) > /dev/mirror/gm0s3d: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mirror/gm0s3d: clean, 84638779 free (1779 frags, 10579625 blocks, > 0.0% fragmentation) > /dev/ad8s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/ad8s1d: clean, 6625471 free (47 frags, 828178 blocks, 0.0% > fragmentation) > THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: > mfs: md (/tmp) > Unknown error; help! > NEnter full pathname of shell or RETURN for /bin/sh: > The problem is, I'm sure, is essentially identical to that described in, > http://www.mail-archive.com/freebsd-current@freebsd.org/msg21675.html > namely that the entry for the memory filesystem, /tmp, in /etc/fstab > is confusing fsck. My /etc/fstab looks like, > # cat /etc/fstab > # Device Mountpoint FStype Options Dump > Pass# > /dev/ad8s1b none swap sw 0 0 > /dev/ad8s1a / ufs rw 1 1 > md /tmp mfs rw,-s64m > 2 2 ^^^ [1] > /dev/ad8s1f /usr ufs rw 2 2 > /dev/ad8s1e /var ufs rw 2 2 > /dev/ad8s1d /var/tmp ufs rw 3 3 ^^^^^^^^^^ [2] > /dev/mirror/gm0s1d /svn ufs rw 2 2 > /dev/mirror/gm0s2d /data ufs rw 2 2 > /dev/mirror/gm0s3d /music ufs rw 2 2 > I can get the system to boot quite happily by carrying on into single > user mode and exiting, but I still get the same behaviour next reboot. > Does anyone have any suggestions? [1] According to man(5) fstab: ----- The sixth field, (fs_passno), is used by the fsck(8) program to determine the order in which file system checks are done at reboot time. The root file system should be specified with a fs_passno of 1, and other file systems should have a fs_passno of 2. File systems within a drive will be checked sequentially, but file systems on different drives will be checked at the same time to utilize parallelism available in the hard- ware. If the sixth field is not present or is zero, a value of zero is returned and fsck(8) will assume that the file system does not need to be checked. ----- Seems that you need to use "0" istead of "2". I'd say the same for the fifth field here. BTW, I can't find what does [2] mean (the values "3" here)... WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve