#moosefs — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #moosefs, aggregated by home.social.
-
@yehor Do you need shared storage? #ZFS replication works very well, even with gigabit Ethernet. It can be a little hard on SSDs but even decent consumer drives should be fine (enterprise drives with PLP are first prize though). It's the option I've gone for with my three node ThinkCentre cluster.
Another option is #MooseFS, which I have heard works well, although you do need to install and manage it outside Proxmox. https://moosefs.com/
-
I'm not sure how this happened but it did. I decided to give #linstor a try since I'm using #incus and it supports it as a back end. I now have a software defined block storage platform, distributed file system with #moosefs and using a vgw as a objectstore gateway backed by moosefs.
The fuck is going on!!
-
Finally moved over to #MooseFS and put Versity Object Store Gateway on top of it. I also set up a side little network that splits replication traffic and client serving traffic that took way to fucking long.
-
Aight.. So.. After fucking with this thing for the better part of the week in the #homelab. I have thoughts.
#seaweedfs! Feels like an open-source project. It's aight so far, it's not as simple as you would think with it being one go binary, it's simple with one go binary. Feels like that nerdy ass teenager you knew about in high school. Fucked with the cool kids and was super smart.. Just never really felt like they were part of the crew! Yea this feels like that!
#moosefs Feels like a product! It's robust, I never really had to fuck with it after setup, solid way of getting shit done, been around for ever.. You gotta pay for the exra shit tho!... It feels like that plastic lining your grandma had on her couches! Fucking old, but that shit was always clean! This felt like grandma's house!
-
I got #seaweedfs working in the #homelab now the way I want it ( possibly). I also came up on some 3.8 TB Micron 5120 or something enterprise ssd's that are 2 years old but still have 100% and 97% of it's life left according to smartclt. I'm still using #moosefs and I don't know how I got here :)
-
Started my distributed file system journey with #moosefs . Been rock solid. Then I found #seaweedfs and it comes with a build in s3 gateway, It's built in go.. Seems simple enough to give it a try in the #homelab . Have we lost the ability to write documentation..just code! . 2 hours later. I have 7 terminal tabs open all running a 4 specific process to get this thing working.. and its still not working! 😂. Documentation says. Just run ./this_fucking_command. Then run ./this_fucking_command and the thing is up.. simple.
-
With #moosefs you can tell it how many copies of files to keep across the storage system. I initially was keeping 2 copies of media files that don’t really need a second copy. Saving me a bunch of money on my car insurance. Of course the efficiency isn’t the same as using raidz or something. I’m rather enjoying the flexibility of the file system. It’s pretty simple and resilient so far. Weakest link is only 1 master!
-
It's not as efficient as some storage options out there with #zfs , but I have been impressed with #moosefs . It's surprising pretty resilient! I don't know if it's performant ( not one of my needs) but has unlocked a shit ton of space in some hard drives I otherwise would be using a tiny bit of. The only thing I'm not a fan of is.. It's not really a fan of thing disappearing and reappearing, like a reboot of a host or something. I know I fucked up when all my hosts start spinning up fans as shit start replicating.
-
I recently moved off #zfs to #moosefs ( it's been great to be honest). I still use some infra that uses zfs but as a loop back file system ( i don't even know if that's an industry term). Anyways, my backups have been pretty slow on it and for some reason it's bugging me. I'm thinking of going back to at least one of my drives be backed by zfs and mount moosefs like I had it before.
-
It's a crazy to think that by using #moosefs , I have a total of 2.8 TB of nvme storage and 32 TB of HDD storage. Which was locked up by ZFS and my use of it. Now of course this isn't apples to apples, but now i'm rolling it bits I didn't really need!
-
Systemd can be a bit of a pain in the ass in a LXC container.. My #moosefs chunkserver were all failing because it needs tailscaled started and whatever I tried it didn't work.. I had to add a entry in my hosts file.. It felt dirty doing it.. I sort of liked it 😆
-
The one observation I did make for #moosefs , is that it does pretty good with sequential large files.. It doesn't really do that well with random read and writes.. Or maybe i'm doing it wrong!! cause that bitch is sloooooowowowow!!
-
I"m slowly setting up #moosefs to house my files. It absolutely isn't as efficient with files as something like #zfs . However, the flexbility
to just add any sized hard drives any where on any system in your #homelab is kinda amazing.
#selfhosted #selfhosting -
I saw #moosefs posted out there... Trying a distributed filesystem seems dope, but I wouldn't have anything to really take advantage it except media.. I guess!
-
@sstranger @andy_warb @zigbee @homeassistant
I haven't had speed issues with my sensors. I moved my zigbee from a huzbsb-1 to a conbee II so that I could run #zigbee2mqtt on a different HC2 than the one I run #zwavejs on. I run HA on a 3rd since I have several odroids I'm using as #moosefs chunkservers and don't need to jam them all into one machine.
A stronger mesh is always a good thing though.
-
@jitteringrunt @kevinbrownsilva @bland_one @martijn_vdijk @homeassistant
Currently I'm running shinobi in a container on one of my ubuntu servers and having it store the video footage on my #moosefs distributed filesystem.
I've got looking at Frigate in my backlog, though.
