Date: Mon, 27 Oct 1997 18:35:24 -0600 From: James Buszard-Welcher <james@reef.com> To: Greg Lehey <grog@lemis.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Recovering Lost Inode? Message-ID: <3455334C.D2AD37F6@reef.com> References: <3454F51C.C37E37EB@reef.com> <19971028095703.58858@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Greg Lehey wrote: > > On Mon, Oct 27, 1997 at 02:10:04PM -0600, James Buszard-Welcher wrote: > > I had a daemon writing to a file... I then rm-ed the file, but the > > daemon still had the filehandle and was writing to it. > > > > Well... I killed the daemon, which had been writing to this invisible > > inode. > > > > Is there ANY way (fsdb, fsck, some great perl hack) to find out what > > this inode was and link it back into some directory so I can get at > > the file contents? > > Not after you stopped the daemon. Then the link count goes to 0 and > the file is removed. > > Greg -- James Buszard-Welcher | VOX 847.729.8600 | "It's not the stuff... Technical Director | FAX 847.729.1560 | it's the power to Silicon Reef, Inc. | PGR 800.418.0016 | *MAKE* the stuff."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3455334C.D2AD37F6>