🚀 go-pugleaf

Tony Nugent (T.Nugent@sct.gu.edu.au) wrote:
: drew@chopper.poohsticks.org (Drew Eckhardt) writes:

: >In article <46vke4$lu5@tornix.tornado.be>,
: >Jan Van Overbeke <jan.vo@tornado.be> wrote:
: >>Tony Nugent <T.Nugent@sct.gu.edu.au> wrote:
: >>>Is there a file recovery tool about the place that I could use to get
: >>>them back?  (I couldn't spot anything on sunsite).

: >No.

: >Run debugfs on the damaged filesystem, do an lsdel to find the files 
: >you're interested in, and use dump <inode #> output_file where the 
: >inode # is in angle brackets.

: debugfs (in the e2fsprogs-0.5b package - although I now notice the
: announcement of version 0.5c) did the trick!  :-)

Great!

: The dump <inode> file command sequence recovered most of the
: files less than 12K (why this limit?), usually with trailing garbage.

This is because you are getting the entire blocks, and not just the
portion used by your file.

: The reading that I did about the ext2 filesystem told me that
: eventually an undelete capability will be part of the system in the
: future (although I won't old my breath for this to happen:)

I don't think that it is really that far off.

: I'll be putting in a "safe-delete" facility for command-line use soon,
: but I accidently deleted these files using a filemanager program...
: circumventing system calls to rm() would be a lot harder to cope with
: :-)

: (BTW, must look at lde real soon... sounds like a good tool to use
: with debugfs).

It sounds sort of like fsdb; does anyone know whether that is a valid
equivant?  If so I would encourge system packagers to include it.