[lkml]   [1996]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Drawbacks of implementing undelete entirely in user space
On Mon, 24 Jun 1996, Stephen R. van den Berg wrote:

> Miquel van Smoorenburg <> 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.

Hmm, well it dosn't happen if .wastebasket dosn't exist, (I would have a
partition wide one anyway), and a hardlink before unlinking the link that
we've (unlink()'s) been asked to remove shouldn't be much overhead, and
no additional disk space ....

> --
> Stephen R. van den Berg (AKA BuGless).
PGP key pass phrase forgotten, \ Overload -- core meltdown sequence
again :( | initiated.
/ This space is intentionally left
| blank, apart from this text ;-)

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