From owner-freebsd-bugs Sat Mar 16 22:40: 5 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B484637B419 for ; Sat, 16 Mar 2002 22:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2H6e2N65141; Sat, 16 Mar 2002 22:40:02 -0800 (PST) (envelope-from gnats) Date: Sat, 16 Mar 2002 22:40:02 -0800 (PST) Message-Id: <200203170640.g2H6e2N65141@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Crist J. Clark" Subject: Re: misc/35992: /etc/rc has no way to force fsck -y at next boot, corrupt filesystems with soft updates required manual intervention Reply-To: "Crist J. Clark" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/35992; it has been noted by GNATS. From: "Crist J. Clark" To: Roy Hooper Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/35992: /etc/rc has no way to force fsck -y at next boot, corrupt filesystems with soft updates required manual intervention Date: Sat, 16 Mar 2002 22:34:31 -0800 On Sun, Mar 17, 2002 at 01:17:29AM -0500, Roy Hooper wrote: > fsck_y_enable="YES" might not trigger fsck-y at the next reboot as it relies > on fsck -p to make it's decision. In my case, it wasn't triggering fsck -y > ever at reboot beacuse it thought the filesystem was clean when it was not. # echo 'fsck -y' >> /etc/rc.early -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message