🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: aus.computers.linux
Article #59786

Re: undelete / unrm / file recover for linux?

#59786
From: Tony Nugent
Date: Wed, 22 Nov 1995 00:00
58 lines
3648 bytes
spc@leroy.cc.uregina.ca (SaskPower) writes:

>So many people keep asking for an undelete on Linux..... (sigh).
>Due to the nature of a multi-tasking (I mean a REAL one like linux)
>operating systems, you cannot expect to do it the way DOS does.

Well if anyone expects to do _anything_ with Linux the way that other
brain-dead OS does, then they shouldn't be using Linux! :-)

>DOS uses a disk allocation scheme which ensures that the NEWEST
>freed up space is not reallocated for a while, so you CAN recover
>a file if you have not generated a LOT of new ones before you
>attempt recovery.  This only works reliably if you don't have several
>other concurrent users ALSO generating a bunch of files, so any
>multitasking O/S generally does not do this.

An `undelete' feature IS planned for the ext2 filesystem.  The
"infractructure" is already there (always has been).  It just hasn't
been implemented yet.  (Just check out the specifications for it; the
basics are already there).

You can use debugfs from the e2fsprogs package to recover files.  But
it's a tricky business, especially when recovering long files that
have indirect inode references in the primary inode block.  But it can
be done (I've done it).

>What you CAN do if you must:

>Use either GNU mv or BSD mv which have OPTION flags to prevent

Yeah, easy enough to do.  There's such a package already available on
sunsite.unc.edu.  But what if you are using a filemanager or whatever
and going through an unlink(2) system call?  (I suppose that you make
sure you have a `safe delete' option turned on :)

>The linux FAQ says this kind of thing is possible, (Question 4.1)
>but does not give details... Since this question is ASKED so often,
>maybe these rough details should be included...

I agree.  debugfs is the current - but rather crude - way to do it.

>I personally don't think Theodore T'so should be spending time
>with an undelete to ext2 filesystem to handle this, as the above is
>so easy to confiugure to your needs and would be more reliable
>than changes to a filesystem... ext2 is just GREAT the way it is... 8^)

Again, in complete agreement.  But from what I can gather, it is being
worked on.  I've got no idea why it's taking so long though.

Cheers
Tony
     o o o o o o o . . .
     o      _____              _______________ __________________=======_||__
   .][__n_n_|DD[  ====_______| |Griffith Uni | | T.Nugent@sct.gu.edu.au     |
  >(||      |  | [Tony Nugent] |Brisbane Aust| | tnugent@gucis.cit.gu.edu.au|
    )_______|__|_[___________]_|_____________|_|____________________________|
  _/oo QGQGQ oo` 'ooo     ooo` 'o!o!o   o!o!o` 'o!o                      o!o`
 -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+-+-+-
Technical Details
Message-ID: <48tplc$8pi@ngriffin.itc.gu.edu.au>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <EKU.95Nov17105401@delphi.philosys.de> <48l805$e4d@sue.cc.uregina.ca>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f5392,355ac0499e9cf894
X-Google-Attributes: gidf5392,public
X-Google-Thread: 10c696,355ac0499e9cf894
X-Google-Attributes: gid10c696,public
X-Google-Thread: 1103af,355ac0499e9cf894
X-Google-Attributes: gid1103af,public
X-Google-Thread: 102983,355ac0499e9cf894
X-Google-Attributes: gid102983,public
From: Tony Nugent <T.Nugent@sct.gu.edu.au>
Subject: Re: undelete / unrm / file recover for linux?
Date: 1995/11/22
Message-ID: <48tplc$8pi@ngriffin.itc.gu.edu.au>
X-Deja-AN: 119860890
references: <EKU.95Nov17105401@delphi.philosys.de> <48l805$e4d@sue.cc.uregina.ca>
organization: Griffith University Brisbane Queensland Australia
reply-to: T.Nugent@sct.gu.edu.au
newsgroups: aus.computers.linux,comp.os.linux.development.apps,comp.os.linux.misc,comp.os.linux.development.system