Building an inode
Hi again, coming back to my problem with the inode of my home directory having disappeared, I found out that the tool ffs2recov from the ports is able to establish an inode entry for a directory where you can explicitely name the inode and the directory. I know which inode number my former home directory had, and of course I know its name. Would it be sufficient to % fs2recov -c 12345 -n poly ad0s1f.dd I think there's more to establish an intact directory structure. As far as I've already learned, when walking back the path from a file deep within a directory structure, every inode contains a field where it comes from, let's say, where CWD and .. are (as an inode number): bla.txt dingens/ foo/poly// 12380 - 12370 - 12360 - 12345 - 2 This would be /home/poly/foo/dingens/bla.txt on ad0s1f (where / is then mounted as /home). When I can assume that every inode still knows where it came from, what would be a useful tool to build poly/ (12345) again? I think I'll need to construct its content again, because just by creating poly/ as 12345, where does the filesystem know from what's the content of poly/? Is the term directory slots I came across related to that topic? Which sources could give good hints? Sadly, fsck_ffs doesn't do the job... but maybe if I fix the file system a bit (instead of fixing fsck_ffs)...? Hey, it's not that I try to build my own nuclear plant in the living room... :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building an inode
On Thu, Oct 30, 2008 at 03:35:04AM +0100, Polytropon wrote: Hi again, snip This is really a question for -fs or -hackers. -questions is for generic stuff -- what you're doing is fairly low-level. Try re-posting your question to -fs, wait a week, then try -hackers. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building an inode
On Wed, 29 Oct 2008 19:47:47 -0700, Jeremy Chadwick [EMAIL PROTECTED] wrote: This is really a question for -fs or -hackers. -questions is for generic stuff -- what you're doing is fairly low-level. Try re-posting your question to -fs, wait a week, then try -hackers. I'll do that, thanks! I hope I'll be able to understand the answers because I'm quite new to low-level stuff. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Building an inode
On Wed, 29 Oct 2008 19:47:47 -0700, Jeremy Chadwick [EMAIL PROTECTED] wrote: Try re-posting your question to -fs, wait a week, then try -hackers. Thank you for this advice, I'll do that - after rewriting the message I prepared. I'm stupid: writing a message and experimenting with ffs2recov is a bad idea. :-) panic: ffs_write: type 0xc5d37e04 0 (0,16384) Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
