Date: Tue, 30 Oct 2001 14:21:04 +0000 From: Ian Dowse <iedowse@maths.tcd.ie> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: bde@zeta.org.au, julian@elischer.org, fs@FreeBSD.ORG Subject: Re: physical block no -> name of file (FFS)? Message-ID: <200110301421.aa17773@salmon.maths.tcd.ie> In-Reply-To: Your message of "Tue, 30 Oct 2001 14:00:19 %2B0100." <200110301300.f9UD0KD05773@Magelan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200110301300.f9UD0KD05773@Magelan.Leidinger.net>, Alexander Leiding er writes: >fsck_ffs may give me a hint how the physical representation on the disk >looks like (if nobody points me to a better documentation). You could try the hacky perl script that I sometimes use for data recovery etc which is at: http://www.maths.tcd.ie/~iedowse/FreeBSD/ufs.pl I'm not sure it will work correctly for you, but it does output block numbers for each file in a filesystem. The output for an inode should look something like ... ino 141227 reclen 0x18 type 010 namelen 14 name 'bsd.gnome.mk,v' 141227 -r--r--r-- 1 1147 0 17465 <date> /Mk/bsd.gnome.mk,v blocks: 0:606824 1:606832 2:606840 3:606848 4:604084 ... where each entry in the "blocks:" list is of the form <lbn>:<blockno>, with the "blockno" measured in units of fragments (fs_fsize) from the start of the partition. "lbn" is the offset from the start of the file in units of fs_bsize blocks. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi? <200110301421.aa17773>