Oops

[MossCommuter]

damn, damn, damn, damn, damn, damn

phil@apu:~$ sudo mount --bind /home/phil/Music /home/ftpuser/Music
:
:
:
[some time later]...

phil@apu:~$ sudo rm -rf /home/ftpuser/

damn, damn, damn, damn, damn, damn

 

[gannet]

oops

you have a backup right ?

 

[MossCommuter]

oops

you have a backup right ?

ahem... a fairly recent one...

apu is my online backup box so I'm reverting to the offline one (removable hard-drive) which is a month or two old

 

[JamesAC]

I DO like the "rm -rf". As in DON'T!

Once, in my professional capacity as a DBA, along with my colleague the Sysman, decided to do a "rm -rf" logged in as root, from \.

We must have been eating the wrong sort of mushrooms!

Fortunately, we did have a current backup of our data, and descriptions of the partitions and so on, and so were able to rebuild unix on our Alpha box, and restore the data.

Folks .. it's almost NEVER too late to back up your data!!

 

[2Loose]

Umm. Oh dear.

 

[Dan B]

http://projects.izzysoft.de/trac/ext3undel/wiki/ext3undel - is this any good to you? I've not used it myself, I'm just googling

It is for occasions like this that I have an external usb disk and an rsnapshot cron job that backs up onto it four times a day

 

[MossCommuter]

http://projects.izzy.../wiki/ext3undel - is this any good to you? I've not used it myself, I'm just googling

It is for occasions like this that I have an external usb disk and an rsnapshot cron job that backs up onto it four times a day

thanks for looking...

Those scripts rely on Foremost which gave a segmentation fault - no matter anyway. I went back to a old backup and managed to get any recent music downloads off of my MP3 player.

Nothing lost I think.

thanks again

 

[Carwash]

I'm sorry for your loss. Doing 'rm -rf' as root is always fraught with danger. I hope you managed to recover your data.

This calls to mind the following quote from the Scary Devil Monastery:

"Sir, Sir! I've deleted all my files."
"Yes my child, and pray tell me how."
"I wanted to delete directories 'fred1' and 'fred2' but I typed 'rm -rf fred *' when should have typed 'rm -rf fred*'."
"Ah ha, and what have you learned?"
"To beware of powerful file-name globbing facilities that my shell provides for my careful use."
"Yes my child, you have learnt a painful lesson. Now you must learn how to recover files from one of the many, multiply redundent backup tapes you have carefully written every evening ever since you were granted a powerful personal workstation."
"Master, I'm eager to learn!"

 

[GrasB]

I'm sorry for your loss. Doing 'rm -rf' as root is always fraught with danger. I hope you managed to recover your data.

This calls to mind the following quote from the Scary Devil Monastery:

"Sir, Sir! I've deleted all my files."
"Yes my child, and pray tell me how."
"I wanted to delete directories 'fred1' and 'fred2' but I typed 'rm -rf fred *' when should have typed 'rm -rf fred*'."
"Ah ha, and what have you learned?"
"To beware of powerful file-name globbing facilities that my shell provides for my careful use."
"Yes my child, you have learnt a painful lesson. Now you must learn how to recover files from one of the many, multiply redundent backup tapes you have carefully written every evening ever since you were granted a powerful personal workstation."
"Master, I'm eager to learn!"

* is evil, use with extreme caution.... bash implements some regex which is much more reliable the rm command becomes:
rm -rf fred[12]
not fail safe from typos but much less likely to cause problems.

 

[Shaun]

The old "rm -r *" chestnut eh? Gets 'em every time!!

 

[Wobblers]

I, along with most sys admins, am currently uttering a blessing starting "There, but for the grace of god... "

But on the bright side, at least you won't do that again!