Live data from Hacker News

File systems unfit as distributed storage back ends: 10 years of Ceph

muratbuffalo.blogspot.com

1–10 of 37 posts

Re: File systems unfit as distributed storage back ends: 10 years of Ceph

#5
post #2

Hi! This could have been submitted as an HTTPS link.

I assume if the owner of the site wanted to redirect all http->https traffic they would do so.

Doing that doesn't actually solve the problem though. A MITM attacker still gets to read and modify all that content.

Re: File systems unfit as distributed storage back ends: 10 years of Ceph

#6
post #5

Earlier quoted context omitted.

I assume if the owner of the site wanted to redirect all http->https traffic they would do so.

Doing that doesn't actually solve the problem though. A MITM attacker still gets to read and modify all that content.

It’s true. Why, just as I was loading the page, someone replaced all instances of “filesystem” with “butt”! The nerve!

Re: File systems unfit as distributed storage back ends: 10 years of Ceph

#7
post #4

I found the story of how Backblaze stores things "on top of", versus "in" filesystems similarly interesting. https://www.backblaze.com/blog/vault-cloud-storage-architect... It seems like they could go one further and eliminate the ext4 underneath.

You'd love this: https://maisonbisson.com/post/object-storage-prior-art-and-l...

Talks about Facebook, Instagram, S3 and other Object Store services and how they deal with storage at scale.

Re: File systems unfit as distributed storage back ends: 10 years of Ceph

#8
post #5

Earlier quoted context omitted.

Doing that doesn't actually solve the problem though. A MITM attacker still gets to read and modify all that content.

It’s true. Why, just as I was loading the page, someone replaced all instances of “filesystem” with “butt”! The nerve!

[deleted]
Post reply on HN