A way to recover deleted files (just contents) from USF2

Wes Peters wes at softweyr.com
Wed Apr 21 21:42:21 PDT 2004

On Tuesday 20 April 2004 05:50, Steve Ames wrote:
> On Tue, Apr 20, 2004 at 08:14:23PM +0800, Xin LI wrote:
> > On Tue, Apr 20, 2004 at 12:26:32PM +0200, Oliver Brandmueller wrote:
> > > This is a FAQ. Und the frequent answer is:
> > >
> > > You can easily recover valuable data after accsional deletion from
> > > your backup. If you don't have a backup, then your data don't seem to
> > > be woth having them backed up.
> >
> > Some Unix coursebooks even comment the result of accidentialy removal
> > of a file without backing up as "User should take this as a lesson".
> That's kinda silly. Unless files are backed up at every edit then most of
> us only have periodic filesystem backups. Lets say I just download a 150M
> file and then accidentally delete it. Rather than wasting time and
> bandwidth downloading again it'd be simpler to just 'unrm' it. Odds are
> that diskspace and even inode haven't been recycled yet.
> Mind you such an option takes some of the breathtaking fun of working
> without a net away from your shell session but hey... sometimes you
> actually do need the airbag.

The easy way to implement this is to make a 'remove file' command that 
really doesn't remove the file.  Yeah, it's that trivial.  When the user 
says 'rm file' you move it into a holding area and note it's original 
location, and when the user says 'unrm file' you put it back.  It doesn't 
free any of the disk space, but it does conceptually get it out of the 
user's face.  Then you add a command to clear out the temporary holding 
area.  We can call that holding area the 'trash can' and the program 
'empty.'  (If you're a VMS-head, you might be tempted to call it 'purge.')

Yes, this can all be done with a few lines of scripting.  Inevitably some 
damn fool is going to want an 'unempty' program too.  We'll let YOU write 
that one.


        Where am I, and what am I doing in this handbasket?

Wes Peters                                               wes at softweyr.com

More information about the freebsd-current mailing list