Date: Tue, 28 Oct 1997 15:30:59 +1030 From: Greg Lehey <grog@lemis.com> To: James Buszard-Welcher <james@reef.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Recovering Lost Inode? Message-ID: <19971028153059.20678@lemis.com> In-Reply-To: <3455334C.D2AD37F6@reef.com>; from James Buszard-Welcher on Mon, Oct 27, 1997 at 06:35:24PM -0600 References: <3454F51C.C37E37EB@reef.com> <19971028095703.58858@lemis.com> <3455334C.D2AD37F6@reef.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 27, 1997 at 06:35:24PM -0600, James Buszard-Welcher wrote: > Thanks for the response. I'm sure it's too late now, with inode > recycling, etc. However, if I had been unable to umount the > filesystem... (we now enter the theoretical zone) > *could* I have been able to use somekindof Norton's Utilities-esque > package for UNIX which could check inodes and look for ones that > were 'file starters', and maybe check the that if all of the inodes > pointed to by that starter inode (it was big file so I excect > a level or two of inode redirection) were still intact it could > pull it back? Kinda like an 'un-delete' fsck? Ever hear of > such a thing? Good question. I don't have a good answer. The first big problem is identifying the inode. You could have literally millions to check. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971028153059.20678>