From owner-freebsd-arch Sat Oct 21 16:43: 4 2000 Delivered-To: freebsd-arch@freebsd.org Received: from des.thinksec.com (isdn-25.follo.net [195.204.140.114]) by hub.freebsd.org (Postfix) with ESMTP id CF32437B4C5 for ; Sat, 21 Oct 2000 16:42:58 -0700 (PDT) Received: (from des@localhost) by des.thinksec.com (8.11.1/8.11.1) id e9LNgpX51590; Sun, 22 Oct 2000 01:42:51 +0200 (CEST) (envelope-from des@thinksec.com) X-URL: http://www.ofug.org/~des/ To: arch@freebsd.org Subject: Ideas concerning fsck From: Dag-Erling Smorgrav Date: 22 Oct 2000 01:42:50 +0200 Message-ID: Lines: 27 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What do people think about dispensing with the Pass# argument in fstab and instead using the following algorithm for 'fsck -p': 1) if the device does not begin with a slash, assume this is a pseudo-filesystem, and skip this entry. 2) if the mountpoint is "none", skip this entry. 3) if the fs type is known, run the appropriate command (which can be null, e.g. for cd9660), and skip to the next entry. 4) if the fs type is unknown, but fsck_${fstype} exists, run it and skip to the next entry. 5) print a big fat "Unknown file system type" warning and skip to the next entry. As for which order to fsck file systems in, do / first, and everything else in parallell afterwards (possibly with additional logic to try to identify file systems that are on the same device and fsck them sequentially to avoid thrashing) I'm willing to write the code if people think it's a good idea. DES --=20 Dag-Erling Sm=F8rgrav - des@thinksec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message