Is there any way I can recover a file called script.sh if I did an rm on it?

Please, this was a script built after posting many questions on this forum, I'll be floored if it's gone...

If you have done an rm it is not recoverable !!!

kinetik, you are floored. Data recovery is your only option now. Best of luck.

Later

You have to grep through the partition it was stored on. There are threads on this...

http://www.linuxquestions.org/questi...d.php?t=428962
http://www.linuxquestions.org/questi...grep+partition

Since the file you want is just a text file, the data you want will be obvious.

grep -a --colour -A3 -B1 /dev/<partition> <some text you know is in the file you want to find>

what filesystem are you using?

if its ext3, its gonna be tough

I assume that going back to the forum/thread where it was delveloped won't work.

Thanks all for replying. Unfortunately I found myself with my heart sunk into my shoes... The script was built following the advice from numerous threads, the code I used isn't in the threads itself.

What really P.O.ed me was that the system didn't even do a confirmation, it just deleted it from the word go, or in this case the word "rm".

But not to be punched out, I've already started rebuilding it, it's now at about 50%. It's faster, smaller and more effective than the old one was so far, uses fewer external scripts and is generally just darn better!
So take that, rm!

Speak to you all again later when the script is at 100%.

Well, it assumes you know what you want when you type it. They say Linux is for gurus and we are not supposed to have someone, like Billy boy, hold our hands.

Don't feel to bad, I once did a rm -rf /* and that was fun. Since I didn't use the -v option I didn't realize what I did until it stopped. It stopped when it got almost done with /sbin. Then it complained about a missing file. Yup, I did a reinstall of Gentoo.

It could be worse. At least your new script is faster.

"They say Linux is for gurus..." <- I agree, but even gurus suffer from absent-mindedness. In fact, I think gurus probably suffer more from absent-mindedness than anyone else!

Anyway, why does it ask for confirmation when logged in as root, but not when logged in as a normal Joe-Schmoe user?

That's just messed up!

It also illustrates my point = The root user is probably the "guru" who is absent-minded, the OS better ask him/ her if he/ she is absolutely sure they want to rm this file. The average user is probably an accountant or a lawyer who suffers from tunnel-vision-thinking, no need to ask them since they probably don't know what the hell they're doing anyway!

In my case the "guru" logged into a normal user account without receiving the "guru-benefits" associated with root!

Haha! I'm just yanking a few laughs out of my predicament now. Anyway, thanks all.

Heres something you might find helpful:

mkdir ~/.trash

then make a script called 'can':

#!/bin/bash
mv $1 $HOME/.trash

Put this in your path. Then instead of using 'rm xxx' use 'can xxx' and move files to .trash folder where you can go through them later and delete.

It will assume the superuser has authority to do everything - you are always strongly warned about doing anything as root. As a regular user you get:... for example.

Your experience is one of the many reasones you keep hearing that you should not log in as root and be very wary of anything you do as root.

easy to prevent that - just alias rm to "rm -i" in a config file.

also do the same for mv and cp while you're at it....

That's just it though. I DID get "rm: remove regular file blabla..." when i WAS logged in as root.
I DID NOT get this when I was logged in as a normal user... The rm command was performed from $, not #.

Not that it matters now, my script is at 100% completion and it's working great! Thanks for all who assisted me (and I needed a whole lot of assisting! )


Thanks friend, I think I will do that in case I rm the wrong file again, which is a very high probability!

Well, no matter how stupid it may seem, the same thing happened to me yesterday.

I had been working on a script (and some auxiliary gnuplot and awk programs) for 2 weeks. I was finished, and wanted to do everything real nice, and cleaned up the copied and temporary files I had created. So I added that to my script.

Uhm, I developed this script in the same directory as were my data files were. Not smart. Because after I executed this part EVERYTHING was wiped out in the directory. Including my scripts!

What happened was that $file2 had not been assigned a value. (a typo somewhere) So what was executed was:

Which wiped out everything. :-(

FORTUNATELY I had the main script file open in an editor, and I could recover most of the contents of other files thru scrolling back the terminal buffer, but boy, I was scared!

To avoid this in the future I added this small test:

Oh, and use another directory for scripting and files.

jlinkels