I saw this on Slashdot and on serverfault. He was using Ansible at the time, and all remote backups were mounted at that time, and wiped clean too.
Yes, catastrophic mistake, but he could recover almost all data with testdisk. I recovered a disk for a colleague once, could recover almost 95%. A journaled filesystem is very good for recovering things. Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. 2016-04-15 14:09 GMT-03:00 Scott Allen <[email protected]>: > On 15 April 2016 at 12:47, D. Hugh Redelmeier <[email protected]> wrote: > > This isn't true of the rm(1) command. No operand means delete nothing. > > The following article gives more specifics: > < > http://www.independent.co.uk/life-style/gadgets-and-tech/news/man-accidentally-deletes-his-entire-company-with-one-line-of-bad-code-a6984256.html > > > > The script actually contained > rm -rf {foo}/{bar} > > The error caused foo and bar to be null so the result was > rm -rf / > > -- > Scott > --- > Talk Mailing List > [email protected] > https://gtalug.org/mailman/listinfo/talk >
--- Talk Mailing List [email protected] https://gtalug.org/mailman/listinfo/talk
