From owner-freebsd-questions Thu Oct 15 13:19:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23178 for freebsd-questions-outgoing; Thu, 15 Oct 1998 13:19:05 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from srv01.bigwheel.net (srv01.bigwheel.net [208.197.88.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23173 for ; Thu, 15 Oct 1998 13:19:03 -0700 (PDT) (envelope-from doug@srv01.bigwheel.net) Received: (from doug@localhost) by srv01.bigwheel.net (8.8.5/8.8.5) id NAA26191; Thu, 15 Oct 1998 13:18:11 -0700 (PDT) Date: Thu, 15 Oct 1998 13:18:11 -0700 (PDT) Message-Id: <199810152018.NAA26191@srv01.bigwheel.net> To: proot@horton.iaces.com From: Doug Jolley Subject: Re: damaged / filesystem Cc: mhughes@logroad.bridge.com, questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Another hint, if 32 is also damaged, you can run: >newfs -N /dev/ to get a list of alternate super blocks. >However if 0 and 32 are damaged, you'll likely not get anything back >anyway. Thanks, Paul, for that very valuable additional information. Fortunately for all of us, these things don't happen very often. Although it can be fairly disruptive when they do, I also try to treat them as an educational experience so I'm better prepared to handle the next such occurrence when it arises. *SO*, the point being that I'm very interested in all these tidbits even though they may not relate specifically to the current disaster, they may well relate to the next. I guess this is all a rather verbose way of saying, "Thanks a batch!" ... doug _____________________________________________________________________ Doug Jolley mailto://doug@footech.com http://www.footech.com Don't bogart that file, my friend. Net it over to me. --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message