From owner-freebsd-questions Fri Feb 27 17:47:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19129 for freebsd-questions-outgoing; Fri, 27 Feb 1998 17:47:51 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19124 for ; Fri, 27 Feb 1998 17:47:44 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id MAA04837; Sat, 28 Feb 1998 12:17:39 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id MAA15726; Sat, 28 Feb 1998 12:17:37 +1030 (CST) (envelope-from grog) Message-ID: <19980228121737.28251@freebie.lemis.com> Date: Sat, 28 Feb 1998 12:17:37 +1030 From: Greg Lehey To: George Vagner , Jerry Dunham , Doug White Cc: FreeBSD Questions Subject: Re: best way to recover References: <199802272333.RAA04423@freeside.fc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802272333.RAA04423@freeside.fc.net>; from Jerry Dunham on Fri, Feb 27, 1998 at 05:33:03PM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 February 1998 at 17:33:03 -0600, Jerry Dunham wrote: > Doug White babbled: >> Date: Fri, 27 Feb 1998 15:20:42 -0800 (PST) >> From: Doug White >> To: George Vagner >> cc: questions@FreeBSD.ORG > >> On Fri, 27 Feb 1998, George Vagner wrote: >> >>> someone said that i should never run fsck on a "live" file system, Yup, that was me. >>> what do they mean by "live" Mounted. >> and is this true? It looks like you found out the hard way. >> well i did run fsck from a remote location and it gave me some errors which i told it to fix >> and upon next boot the system hung. [BTW: Why do you have to write such long lines? I've asked you about this before]. Well, that was clever after being warned, wasn't it? fsck works on the character device and ignores the contents of cache, so it can see deficiencies where none exist. If it "fixes" these deficiencies, it corrupts the disk. >> I booted into single user mode and ran fsck again which it found >> more errors and i told it to fix them. Now the system is back to >> normal i THINK... Probably. >>> what is the best way to make sure that all my binaries are in tact and >>> my kernel is ok? >> >> If they run, you're OK. > > What do you mean? If I understand George's question, he's asking how to > know whether ALL the binaries are okay, and it doesn't seem practical to > run every one to test. Is there any OTHER way to gain a warm fuzzy > regarding one's collection of binary files. Well, yes, that may not be the most accurate criterion. To be 100% sure, you need to compare them with the original, or to read in your last backup. In practice, though, it's unlikely that you've damaged any files which hadn't been modified since the last mount, and that includes most of the binaries. You could go looking for ones which have been modified round the time that you did the fsck, but I don't expect you'll have much trouble. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message