🚀 go-pugleaf

In article <470bko$afc@tech.cftnet.com> jgeorge@cftnet.com (Jonathan George) writes:
   Tony Nugent (T.Nugent@sct.gu.edu.au) wrote:
   : Big oops.  :-(

   : The big rm command happily did it's job, and obliterated a bunch of
   : file that I really wanted to keep.

   : I immediately umount'ed that partition in the hope that the files are
   : still there.

Best you could do.
The contents of the sectors is still there (it couldn't be overwritten
because you unmounted the partition) , but the relation to a file
has been lost irreversably. I don't know of any tool to regain this
relation with the exeption of lde, the linux disk editor.
[...]
   Incidentally, the best chance for recovery might have been to turn off the
   power for your machine before the MBR had a chance to be updated, and then
   use fsck to recover the file system.  On the other hand this could also
   corrupt your filesystem beyond repair; it's really a role of the dice.

Just stupid! The MBR will only(!) be overwritten if you use /sbin/lilo or
DOS fdisk \MBR and it has NOTHING to do at all with the data on the
disk.

   Of course the best solution would be to hack the fsck source to recover
   recently deleted inodes.

And how do you want to keep track on "recently deleted inodes"? 

Greetings jue
-- 
--
Juergen Exner: jue@cs.tu-berlin.de                  FAX: 030/314-73623
snail-mail: TU Berlin; Sekr. FR 5-13; Franklinstr. 28-29; 10587 Berlin
=-=-=-=-= "I'm sorry Dave, but I can't do that"  HAL 2000  =-=-=-=-=-=