4 ms·
> Not sure how fast your disks were, but 300GB gone in "a few seconds" sounds like a stretch. That only depends on the # of files. If it's even a thousand file
by mschuster91 10y ago
> Not sure how fast your disks were, but 300GB gone in "a few seconds" sounds like a stretch.
That only depends on the # of files. If it's even a thousand files, any modern Linux rm -rf will remove them in less time than a blink.
> The theoretically best thing to do in such a situation would probably be to unplug the machine ASAP after ^C (without going through formal shutdown processes that may try to "clean up" unfinished disk work), remove the disk, attach it to a machine with a write blocker, and take a full-disk image for forensics purposes. This would maximize the ability to extract any data that the system was unable to eat/destroy.
Their infrastructure is cloud based. No way to get a physical disk - if there is a "disk" at all and not a couple of huge fat NetApp filers providing the storage to the CPU nodes. (This is how a couple web-hosters operate)