From owner-freebsd-hackers Mon Oct 27 18:26:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA16551 for hackers-outgoing; Mon, 27 Oct 1997 18:26:30 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA16540 for ; Mon, 27 Oct 1997 18:26:12 -0800 (PST) (envelope-from perlsta@cs.sunyit.edu) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.7/8.8.5) with SMTP id WAA01275 for ; Mon, 27 Oct 1997 22:31:26 -0500 (EST) X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Mon, 27 Oct 1997 22:31:26 -0500 (EST) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: freebsd-hackers@FreeBSD.ORG Subject: Re: Recovering Lost Inode? In-Reply-To: <3455334C.D2AD37F6@reef.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i've always wondered why when a file was deleted there was an intelegent way of moving it to a volitile directory where it could be overwritten at any time, but if moved out of that dir it would be marked non-volitile again.... (maybe i've used win95 once too many...) -Alfred On Mon, 27 Oct 1997, 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? > > 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." >