lkml.org 
[lkml]   [1996]   [Jun]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: Drawbacks of implementing undelete entirely in user space
From
In article <199606252322.BAA22853@informatik.uni-koblenz.de> 
Systemkennung Linux <linux@informatik.uni-koblenz.de> wrote:


>> Miquel van Smoorenburg <miquels@cistron.nl> wrote:
[...]
>> 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.

But, unless I'm mistaken, it can't tell you whether or not this has
happened. It will give you a count of which of the file's blocks are
currently free - but these could have been used subsequently by
another, now deleted, file.

So after undeleting you would have to manually check what was
recovered for the presence of garbage (or bits of
/some-file-you-weren't-supposed-to-see).

ray


--
Ray Auchterlounie Research Student (still) at:
<rda@kythera.demon.co.uk> Signal Processing Group
<rda@eng.cam.ac.uk> Cambridge University Engineering Dept.
"Don't ask me about my thesis (TM)"






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