Date: Thu, 15 Oct 1998 13:18:11 -0700 (PDT) From: Doug Jolley <doug@footech.com> To: proot@horton.iaces.com Cc: mhughes@logroad.bridge.com, questions@FreeBSD.ORG Subject: Re: damaged / filesystem Message-ID: <199810152018.NAA26191@srv01.bigwheel.net>
next in thread | raw e-mail | index | archive | help
>Another hint, if 32 is also damaged, you can run:
>newfs -N /dev/<rawdevice> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810152018.NAA26191>