From owner-freebsd-bugs Thu Feb 19 19:45:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01603 for freebsd-bugs-outgoing; Thu, 19 Feb 1998 19:45:18 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01581 for ; Thu, 19 Feb 1998 19:45:15 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id TAA00530; Thu, 19 Feb 1998 19:44:22 -0800 (PST) To: Vince Vielhaber cc: freebsd-bugs@FreeBSD.ORG Subject: Re: gotcha with fsck? In-reply-to: Your message of "Thu, 19 Feb 1998 21:27:30 EST." Date: Thu, 19 Feb 1998 19:44:22 -0800 Message-ID: <526.887946262@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Any suggested workarounds? I *was* planning on putting this machine > into service this weekend at a remote location but I'm thinking I'll > hold off for now (as long as the other machine is still breathing :) Change fsck -p to fsck -y. Problem solved. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message