From owner-freebsd-hackers Sat May 20 13:29:34 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA07921 for hackers-outgoing; Sat, 20 May 1995 13:29:34 -0700 Received: from relay3.UU.NET (relay3.UU.NET [192.48.96.8]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA07883 for ; Sat, 20 May 1995 13:29:19 -0700 Received: from uucp3.UU.NET by relay3.UU.NET with SMTP id QQyqov27425; Sat, 20 May 1995 16:29:15 -0400 Received: from uanet.UUCP by uucp3.UU.NET with UUCP/RMAIL ; Sat, 20 May 1995 16:29:15 -0400 Received: by crocodil.monolit.kiev.ua (8.6.8.1/8.5) id XAA13804 for hackers@FreeBSD.ORG; Sat, 20 May 1995 23:26:32 +0300 Path: newsserv From: Igor Sviridov Newsgroups: cs-monolit.gated.lists.freebsd.hackers Subject: Re: fsck & boot Q Date: Sat, 20 May 95 15:13:32 +0200 Distribution: world Organization: Communication Systems Research Team, Kiev, Ukraine Message-ID: <800972012PCTIN@lot.cs.kiev.ua> Reply-To: sia-@ua.net X-Return-Path: lotua!lot.cs.kiev.ua!sia Apparently-To: hackers@FreeBSD.org Sender: hackers-owner@FreeBSD.org Precedence: bulk In article "Rashid Karimov." writes: > Well, but the Q is : > when it reboots in this way , it cleans all the filesystem > except one , and then prompts for the default shell and asks > sysadm to clean the FS manually.And if noone is available - > the system just sits there forever. > Is there any way to explicitly tell the system to run fsck -y > _automatically on all FSes or at least on those it can't clean > > out ? And after everything is cool - just resume normal operation ? > If it's impossible - can some1 point me to the code which is involved > in that stage of boot process ? Look in /etc/rc, it runs fsck -p, which parses /etc/fstab to find which filesystems in which order to check/repair. Also, if filesystem is trashed harder, than it may be without hardware/software failures, then fsck -p will not repair it and ask for operator intervention. I used to insert "fsck -y /dev/sd0..." in /etc/rc, if "fsck -p" didn't help; though it seems to be undesirable (note, that you usually even don't have place to store message about rough filesystem cleanup :-( ) > Rashid -- Igor