News for hackers. Stuff that matters.

A comment on AWS Snowcone. Parent comment

Re:AWS Snowcone by akersten on Wednesday June 17, 2020 @03:17PM (#23555522)
Those are all really good points. I'm interested in hearing more about the NTFS quirks - what kind of issues were cropping up?

Now I'm really curious what filesystem Snowball wound up standardizing on, and how/if file metadata/ACLs/alternate data streams are maintained.

[ Parent | on HN ]
Re:AWS Snowcone by rainbowzootsuit on Wednesday June 17, 2020 @05:15PM (#23556868)
I helped a client do a transfer to S3 via snowball once for a music studio client with a smorgusboard of random hard drives.

The software client for doing the transfer is some sort of command line JVM tool from my memory. You locally create S3 buckets on the snowball and copy from the local disks into the buckets.

Once the snowball is returned, the buckets appear in your online account.

[ Parent | on HN ]
Re:AWS Snowcone by Twirrim on Wednesday June 17, 2020 @06:08PM (#23557381)
The main issues with NTFS would be the system either wouldn't be able to see the drive, or would fail to be able to read part of it. They were building up quite a repertoire of tricks to get things to read correctly, but it was almost impossible to safely automate.
[ Parent | on HN ]
Re:AWS Snowcone by dylz on Wednesday June 17, 2020 @04:24PM (#23556285)
Do those even matter if the final file destination is S3?
[ Parent | on HN ]
Re:AWS Snowcone by akersten on Wednesday June 17, 2020 @05:04PM (#23556730)
It's mostly a technical curiosity to me. Although maybe they would if you're using it in a system backup/archive workflow?
[ Parent | on HN ]