• SeriousBug@infosec.pub
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    ext4 on an mdadm raid. It works well enough, and supports growing your array.

    Although if I rebuilt this from scratch, I would skip mdadm and just let minio control all the drives. Minio has an S3 compatible API, which I’d then mount into whatever apps need it.

    • mattes@lemmy.kussi.me
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      Love MinIO but it’s not a filesystem and mounting object storage as a filesystem is not a great experience (speaking from commercial experience).

      • aksdb@feddit.de
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Same experience here. S3 is essentially a key/value store to simply put and retrieve large values/blobs. Everything resembling filesystem features is just convention over how keys are named. Comminication uses HTTP, so there is a lot of overhead when working with it as an FS.

        In the web you can use these properties to your advantage: you can talk to S3 with simple HTTP clients, you can use reverse proxies, you can put a CDN in front and have a static file server.

        But FS utils are almost always optimized for instant block based access and fast metadata responses. Something simple like a find will fuck you over with S3.