This is still a common thing. Amazon has AWS Snowball [1] (up to 210 TB), Backblaze has Fireball [2] (96 TB), and I'm sure there are others. [1]: https://aws.amazon.com/snowball/ [2]: https://www.backblaze.com/cloud-storage/features/fireball-data-migration. - Source: Hacker News / 2 months ago

If you have extremely large amounts of data to transfer, such as hundreds of petabytes or into exabytes, AWS Snowmobile can move up to 100PB at once via a ruggedized shipping container. The ruggedized shipping container is tamper-resistant, water-resistant, temperature controlled, and GPS-tracked. The service was announced in 2016, and one of the trucks shown during a presentation that year at AWS re-Invent:. - Source: dev.to / 3 months ago

AWS Snowball has a number of devices optimized for edge computing and data transfer. The service allows you to order a ruggedized device that can hold multiple terrabytes to petabytes of data, to transfer to AWS. - Source: dev.to / 3 months ago

If you have extremely large amounts of data to transfer, such as hundreds of petabytes or into exabytes, AWS Snowmobile can move up to 100PB at once via a ruggedized shipping container. The ruggedized shipping container is tamper-resistant, water-resistant, temperature controlled, and GPS-tracked. The service was announced in 2016, and one of the trucks shown during a presentation that year at AWS re-Invent:. - Source: dev.to / 3 months ago

I'm sure once they got the BC-304s making regular round trips they dropped of a couple of AWS snowmobile trailers. For boosting their computing power and make copies of the Atlantis database to send back to Earth for more in depth analysis. Source: 6 months ago

There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 2 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 2 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 2 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: over 2 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: over 2 years ago