lkml.org 
[lkml]   [1996]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Drawbacks of implementing undelete entirely in user space
Date
Hi,

> Miquel van Smoorenburg <miquels@cistron.nl> wrote:
> >How about moving the deleted file into a directory .wastebasket/XXXXX,
> >where XXXXX is the inode number of the directory the file was in at
> >the moment it was deleted. If that directory has the same permissions
>
> That implies that deleting files could potentially increase the space
> requirement on the disk (not good). Creating a directory is an "expensive"
> operation (uses non-negligible space and cpu/wallclock time).
>
> I don't think those are desirable properties of an unlink() operator.

Indeed, because a single line of extra code in ext2's debugfs makes
undelete possible as long as the file hasn't been physically overwritten
yet.

Ralf


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.062 / U:20.592 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site