home.social

#seaweedfs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #seaweedfs, aggregated by home.social.

  1. 4.25

    Note This is a quick follow up for 4.24. It is safe to upgrade. The erasure coding with multi-disk servers needs to recover automatically from previous failures. The added security checking caused Admin UI not working well. Users with...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage

  2. 4.24

    Important note 4.23 is not safe when there are multiple disks configured and erasure coding(EC) is using the worker. The worker added a capability to distribute EC shards to different disks to ensure proper shard distribution. However, the volume...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage

  3. 4.23 (Not safe for erasure coding and multi-disk volume servers)

    What's Changed Shell fix(shell): correct volume.list -writable filter unit and comparison by @qzhello in #9231 shell: expand ~ in local file path arguments by @chrislusf in #9265 fix(shell): use exact match for volume.balance -racks/-nodes...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage

  4. What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.

    RE: https://sakurajima.social/notes/alt7i6brp4

  5. What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.

    RE: https://sakurajima.social/notes/alt7i6brp4

  6. What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.

    RE: https://sakurajima.social/notes/alt7i6brp4

  7. What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.

    RE: https://sakurajima.social/notes/alt7i6brp4

  8. What ended up working is using #Longhorn itself to backup my #Kubernetes volumes to my #S3 storage (#SeaweedFS), which works regardless of the volumes' access modes. This is fine, tho I still wish I could get #Velero working bcos in theory - it shd be better since it'd work with all storage rather than Longhorn alone... but yea honestly have no idea how to get it working with RWO volumes.

    RE: https://sakurajima.social/notes/alt7i6brp4

  9. "There is a new release of SeaweedFS. Happy updating your instance and don't forget to check the changelog."

    # 4.23

    What's Changed Shell fix(shell): correct volume.list -writable filter unit and comparison by @qzhello in #9231 shell: expand ~ in local file path arguments by @chrislusf in #9265 fix(shell): use exact match for volume.balance -racks/-nodes...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage

  10. "There is a new release of SeaweedFS. Happy updating your instance and don't forget to check the changelog."

    # 4.23

    What's Changed Shell fix(shell): correct volume.list -writable filter unit and comparison by @qzhello in #9231 shell: expand ~ in local file path arguments by @chrislusf in #9265 fix(shell): use exact match for volume.balance -racks/-nodes...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage

  11. @[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/

  12. @[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/

  13. @[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/

  14. @[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/

  15. @[email protected] i'd set up #seaweedfs as s3 storage, and tried to get velero working as means to backup my PVCs, but it ended up not working cos somehow, RWO #longhorn volumes of mine just fail to be backed up :/

  16. I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn

    #kubernetes #homelab

  17. I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn

    #kubernetes #homelab

  18. I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn

    #kubernetes #homelab

  19. I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn

    #kubernetes #homelab

  20. I've set up #velero and #seaweedfs (as the #s3 storage) and yet backups of my pvcs are failing :( it seems that only the RWO vols are failing? but as far as im aware, velero/#kopia shdnt care/differentiate if it's RWO or not? any clue? underlying storage is #longhorn

    #kubernetes #homelab

  21. Argh!

    Debian Trixie maps /tmp directly to RAM—unlike previous versions <= Bookworm!

    Since my Nginx cache is located in /tmp, my RAM filled up in no time after my Trixie upgrade. This, in turn, caused the OOM killer to target SeaweedFS, making the media storage inaccessible.

    Sorry!

    (But the problem has now been understood and fixed).

    #metalheadclub #seaweedfs #mastodon #mastoadmin

  22. Argh!

    Debian Trixie maps /tmp directly to RAM—unlike previous versions <= Bookworm!

    Since my Nginx cache is located in /tmp, my RAM filled up in no time after my Trixie upgrade. This, in turn, caused the OOM killer to target SeaweedFS, making the media storage inaccessible.

    Sorry!

    (But the problem has now been understood and fixed).

    #metalheadclub #seaweedfs #mastodon #mastoadmin

  23. Argh!

    Debian Trixie maps /tmp directly to RAM—unlike previous versions <= Bookworm!

    Since my Nginx cache is located in /tmp, my RAM filled up in no time after my Trixie upgrade. This, in turn, caused the OOM killer to target SeaweedFS, making the media storage inaccessible.

    Sorry!

    (But the problem has now been understood and fixed).

    #metalheadclub #seaweedfs #mastodon #mastoadmin

  24. Argh!

    Debian Trixie maps /tmp directly to RAM—unlike previous versions <= Bookworm!

    Since my Nginx cache is located in /tmp, my RAM filled up in no time after my Trixie upgrade. This, in turn, caused the OOM killer to target SeaweedFS, making the media storage inaccessible.

    Sorry!

    (But the problem has now been understood and fixed).

    #metalheadclub #seaweedfs #mastodon #mastoadmin

  25. Argh!

    Debian Trixie maps /tmp directly to RAM—unlike previous versions <= Bookworm!

    Since my Nginx cache is located in /tmp, my RAM filled up in no time after my Trixie upgrade. This, in turn, caused the OOM killer to target SeaweedFS, making the media storage inaccessible.

    Sorry!

    (But the problem has now been understood and fixed).

    #metalheadclub #seaweedfs #mastodon #mastoadmin

  26. #MinIO Is Done With #OpenSource, What Are Your Options?
    MinIO is one of the most widely used #selfhosted #objectstorage solutions out there. It is #S3-compatible, lightweight, and runs as a single binary, integrating with pretty much everything in the #cloudnative stack.

    Here are the three open source alternatives worth looking at. 👇
    #SeaweedFS
    #Garage
    #RustFS

    I have heard good things about Garage but haven't kicked the tires yet.
    itsfoss.com/news/minio-moves-a

  27. #MinIO Is Done With #OpenSource, What Are Your Options?
    MinIO is one of the most widely used #selfhosted #objectstorage solutions out there. It is #S3-compatible, lightweight, and runs as a single binary, integrating with pretty much everything in the #cloudnative stack.

    Here are the three open source alternatives worth looking at. 👇
    #SeaweedFS
    #Garage
    #RustFS

    I have heard good things about Garage but haven't kicked the tires yet.
    itsfoss.com/news/minio-moves-a

  28. Is Done With , What Are Your Options?
    MinIO is one of the most widely used solutions out there. It is -compatible, lightweight, and runs as a single binary, integrating with pretty much everything in the stack.

    Here are the three open source alternatives worth looking at. 👇


    I have heard good things about Garage but haven't kicked the tires yet.
    itsfoss.com/news/minio-moves-a

  29. #MinIO Is Done With #OpenSource, What Are Your Options?
    MinIO is one of the most widely used #selfhosted #objectstorage solutions out there. It is #S3-compatible, lightweight, and runs as a single binary, integrating with pretty much everything in the #cloudnative stack.

    Here are the three open source alternatives worth looking at. 👇
    #SeaweedFS
    #Garage
    #RustFS

    I have heard good things about Garage but haven't kicked the tires yet.
    itsfoss.com/news/minio-moves-a

  30. #MinIO Is Done With #OpenSource, What Are Your Options?
    MinIO is one of the most widely used #selfhosted #objectstorage solutions out there. It is #S3-compatible, lightweight, and runs as a single binary, integrating with pretty much everything in the #cloudnative stack.

    Here are the three open source alternatives worth looking at. 👇
    #SeaweedFS
    #Garage
    #RustFS

    I have heard good things about Garage but haven't kicked the tires yet.
    itsfoss.com/news/minio-moves-a

  31. От MinIO к SeaweedFS: опыт замены S3-хранилища

    Есть такой опасный момент в инфраструктуре: когда все вроде бы работает, но трогать это лишний раз не хочется. Не потому что идеально. А потому что есть ощущение — если полезешь, станет хуже. В какой-то момент мы поймали себя на этом с MinIO.

    habr.com/ru/companies/dbraincl

    #seaweedfs #minio #s3 #хранилище #кубернетес #kubernetes #контейнеризация #s3хранилище #инфраструктура #ceph

  32. От MinIO к SeaweedFS: опыт замены S3-хранилища

    Есть такой опасный момент в инфраструктуре: когда все вроде бы работает, но трогать это лишний раз не хочется. Не потому что идеально. А потому что есть ощущение — если полезешь, станет хуже. В какой-то момент мы поймали себя на этом с MinIO.

    habr.com/ru/companies/dbraincl

    #seaweedfs #minio #s3 #хранилище #кубернетес #kubernetes #контейнеризация #s3хранилище #инфраструктура #ceph

  33. От MinIO к SeaweedFS: опыт замены S3-хранилища

    Есть такой опасный момент в инфраструктуре: когда все вроде бы работает, но трогать это лишний раз не хочется. Не потому что идеально. А потому что есть ощущение — если полезешь, станет хуже. В какой-то момент мы поймали себя на этом с MinIO.

    habr.com/ru/companies/dbraincl

    #seaweedfs #minio #s3 #хранилище #кубернетес #kubernetes #контейнеризация #s3хранилище #инфраструктура #ceph

  34. От MinIO к SeaweedFS: опыт замены S3-хранилища

    Есть такой опасный момент в инфраструктуре: когда все вроде бы работает, но трогать это лишний раз не хочется. Не потому что идеально. А потому что есть ощущение — если полезешь, станет хуже. В какой-то момент мы поймали себя на этом с MinIO.

    habr.com/ru/companies/dbraincl

    #seaweedfs #minio #s3 #хранилище #кубернетес #kubernetes #контейнеризация #s3хранилище #инфраструктура #ceph

  35. Achtung #Fnordon, jetzt rumpelt's gleich kurz.

    Ich schalte den Object Storage von #MinIO auf #SeaweedFS um. Dadurch könnten vorübergehend Medien (Bilder/Videos) fehlen, die kommen aber alle wieder.

    #Mastoadmin

  36. Achtung #Fnordon, jetzt rumpelt's gleich kurz.

    Ich schalte den Object Storage von #MinIO auf #SeaweedFS um. Dadurch könnten vorübergehend Medien (Bilder/Videos) fehlen, die kommen aber alle wieder.

    #Mastoadmin

  37. Achtung #Fnordon, jetzt rumpelt's gleich kurz.

    Ich schalte den Object Storage von #MinIO auf #SeaweedFS um. Dadurch könnten vorübergehend Medien (Bilder/Videos) fehlen, die kommen aber alle wieder.

    #Mastoadmin

  38. Achtung #Fnordon, jetzt rumpelt's gleich kurz.

    Ich schalte den Object Storage von #MinIO auf #SeaweedFS um. Dadurch könnten vorübergehend Medien (Bilder/Videos) fehlen, die kommen aber alle wieder.

    #Mastoadmin

  39. Achtung #Fnordon, jetzt rumpelt's gleich kurz.

    Ich schalte den Object Storage von #MinIO auf #SeaweedFS um. Dadurch könnten vorübergehend Medien (Bilder/Videos) fehlen, die kommen aber alle wieder.

    #Mastoadmin

  40. "There is a new release of SeaweedFS. Happy updating your instance and don't forget to check the changelog."

    # 4.22

    > Comments For clusters with multiple volume servers with multiple disks, and if Erasure Coding is used, please upgrade! #9219 fixed a problem when the volume server is restarted, some EC shards may be reported as missing while actually they are...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage

  41. "There is a new release of SeaweedFS. Happy updating your instance and don't forget to check the changelog."

    # 4.22

    > Comments For clusters with multiple volume servers with multiple disks, and if Erasure Coding is used, please upgrade! #9219 fixed a problem when the volume server is restarted, some EC shards may be reported as missing while actually they are...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage

  42. "There is a new release of SeaweedFS. Happy updating your instance and don't forget to check the changelog."

    4.21

    What's Changed This is a packed release with many fixes and some new features! FUSE Mount now is 100% POSIX Compliant FUSE Mount added peer-to-peer file chunk sharing! For AI use case, added optimization for all-to-all parallel downloading from...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage

  43. "There is a new release of SeaweedFS. Happy updating your instance and don't forget to check the changelog."

    4.21

    What's Changed This is a packed release with many fixes and some new features! FUSE Mount now is 100% POSIX Compliant FUSE Mount added peer-to-peer file chunk sharing! For AI use case, added optimization for all-to-all parallel downloading from...

    github.com/seaweedfs/seaweedfs

    #seaweedfs #s3 #objectstorage