this post was submitted on 03 Jan 2024
39 points (93.3% liked)

Selfhosted

40296 readers
185 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
39
pooling media libraries - like distributed storage (lemmy.dbzer0.com)
submitted 10 months ago by suntzu@lemmy.dbzer0.com to c/selfhosted@lemmy.world
42 comments fedilink hide all child comments
 

I run a full media server, as well do a few friends. Now we had the idea to share our media libraries. In a first quick attempt we, mounted each other's library folder via an smb share and imported those in jellyfin (all servers connected by VPN) Works quite well, but is kind of cumbersome the more people get in. I had the following idea: distributed storage, not as in redundancy, but more like mergerfs. Each "node" allocates a certain amount of storage, say node A, B and C provide 1TB each, these get fused into a singe mount that shows up as 3TB volume. If one node goes offline, the volume will only be 2TB and all files on the offline node will of course be unavailable.

Did a bit of research and found stuff like ceph,.glusterfs or seeweedfs, all of which I guess have a lot more functionality and thus are quite complicated and a little over my head. Do you do something like that or have any good ideas how to do that easily?

you are viewing a single comment's thread
view the rest of the comments
[–] planish@sh.itjust.works 1 points 10 months ago* (last edited 10 months ago)

I think you can keep doing the SMB shares and use an overlay filesystem on top of those to basically stack them on top of each other, so that server1/dir1/file1.txt and server2/dir1/file2.txt and server3/dir1/file3.txt all show up in the same folder. I'm not sure how happy that is when one of the servers just isn't there though.

Other than that you probably need some kind of fancy FUSE application to fake a filesystem that works the way you want. Maybe some kind of FUES-over-Git-Annex system exists that could do it already?

I wouldn't really recommend IPFS for this. It's tough to get it to actually fetch the blocks promptly for files unless you manually convince it to connect to the machine that has them. It doesn't really solve the shared-drive problem as far as I know (you'd have like several IPNS paths to juggle for the different libraries, and you'd have to have a way to update them when new files were added). Also it won't do any encryption or privacy: anyone who has seen the same file that you have, and has the IPFS hash of it, will be able to convince you to distribute the file to them (whether you have a license to do so or not).