Messages in this thread | | | From | Systemkennung Linux <> | Subject | Re: Drawbacks of implementing undelete entirely in user space | Date | Wed, 26 Jun 1996 01:22:01 +0200 (MET DST) |
| |
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
| |