Date: Wed, 16 Jan 2002 08:29:41 -0500 (EST) From: Chad Ziccardi <ziccardi@digitalfreaks.org> To: Mike Meyer <mwm-dated-1011551443.80cdfb@mired.org> Cc: Annelise Anderson <andrsn@andrsn.stanford.edu>, <Alex.Wilkinson@dsto.defence.gov.au>, <freebsd-questions@FreeBSD.ORG> Subject: Re: Super Block Message-ID: <20020116082830.C20463-100000@digitalfreaks.org> In-Reply-To: <15428.30035.136131.19101@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 15 Jan 2002, Mike Meyer wrote: > Annelise Anderson <andrsn@andrsn.stanford.edu> types: > > On Mon, 14 Jan 2002, Mike Meyer wrote: > > > One-sentence summary of why it's important: It where you start when > > > you want to find a file in the file system. > > Suppose you overwrite a disklabel and haven't made a copy; if you > > can access the slice and you want to write a new disklabel, is > > there any way to find out where the superblocks are? > > Since you don't know the exact sizes, the only way I can think of is > to open the raw disk device, read in struct fs sized chunks at block > intervals, and check fs_magic for "real" superblocks. When you find a > pair that's 32 blocks apart, you've found the superblock and the first > alternate for a file system. Try ffsrecov to find the superblocks on a raw device. ffsrecov -s It's in the ports. -- Chad Ziccardi, Professional Slacker cz@digitalfreaks.org "Some cause happiness wherever they go; others whenever they go." 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?20020116082830.C20463-100000>