101010.pl

Asta [AMP]hey hey <a href="https://fire.asta.lgbt/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://fire.asta.lgbt/tags/FileSystem" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://fire.asta.lgbt/tags/ZFS" rel="nofollow noopener" target="_blank">#ZFS</a> <a href="https://fire.asta.lgbt/tags/RAID" rel="nofollow noopener" target="_blank">#RAID</a> <a href="https://fire.asta.lgbt/tags/XFS" rel="nofollow noopener" target="_blank">#XFS</a> entities! I'm looking for extremely opinionated discourses on alternatives to ZFS on Linux for slapping together a <a href="https://fire.asta.lgbt/tags/JBOD" rel="nofollow noopener" target="_blank">#JBOD</a> ("Just a Bunch Of Disks", "Just a Buncha Old Disks", "Jesus! Buncha Old Disks!", etc) array. I like ZFS but the fact that it's not in tree in-kernel is an issue for me. What I need most is reliability and stability (specifically regarding parity) here; integrity is the need. Read/write don't have to be blazingly fast (not that I'm mad about it). I also have one <a href="https://fire.asta.lgbt/tags/proxmox" rel="nofollow noopener" target="_blank">#proxmox</a> ZFS array where a raw disk image is stored for a <a href="https://fire.asta.lgbt/tags/Qemu" rel="nofollow noopener" target="_blank">#Qemu</a> <a href="https://fire.asta.lgbt/tags/VirtualMachine;" rel="nofollow noopener" target="_blank">#VirtualMachine;</a> in the VM, it's formatted to XFS. That "seems" fine in limited testing thus far (and quite fast, so it does seem like the defaults got the striping correct) but I kind of hate how I have multiple levels of abstraction here. I don't think there's been any change on the <a href="https://fire.asta.lgbt/tags/BTRFS" rel="nofollow noopener" target="_blank">#BTRFS</a> front re: raid-like array stability (I like and use BTRFS for single disk filesystems but) although I would love for that to be different. I'm open to <a href="https://fire.asta.lgbt/tags/LVM" rel="nofollow noopener" target="_blank">#LVM</a>, etc, or whatever might help me stay in tree and up to date. Thank you! Boosts appreciated and welcome. <a href="https://fire.asta.lgbt/tags/techPosting" rel="nofollow noopener" target="_blank">#techPosting</a>

Kevin Karhan :verified:<a href="https://infosec.exchange/@Heidi" class="u-url mention" rel="nofollow noopener" target="_blank">@Heidi</a> DON'T YELL AT YOUR <a href="https://infosec.space/tags/JBOD" class="mention hashtag" rel="nofollow noopener" target="_blank">#JBOD</a>|s THO!<a href="https://www.youtube.com/watch?v=tDacjrSCeq4&t=44s" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=tDacjrSCeq4&t=44s</a>

:nfld_tri: 🇨🇦 CowMan 🇪🇺 🇺🇦 🇲🇽Well, added a storage tier this evening. A couple 4 Tb drives which I had laying about, as <a href="https://nfld.me/tags/JBOD" class="mention hashtag" rel="nofollow noopener" target="_blank">#JBOD</a> (<a href="https://nfld.me/tags/MergerFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MergerFS</a>), for those media files which are "replaceable" and don't really need to be on <a href="https://nfld.me/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> mirrors (~70 & ~16 Tb).I now feed into <a href="https://nfld.me/tags/Plex" class="mention hashtag" rel="nofollow noopener" target="_blank">#Plex</a> from the different tiers using <a href="https://nfld.me/tags/OverlayFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OverlayFS</a>.Pretty neat. I can move things around without Plex noticing, select the tier in <a href="https://nfld.me/tags/Sonarr" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sonarr</a> / <a href="https://nfld.me/tags/Radarr" class="mention hashtag" rel="nofollow noopener" target="_blank">#Radarr</a>, and if one of those 4 Tb drives goes down, NBD and I can see what is missing.More iops don't hurt either.

Recent searches

Search options

Administered by:

Server stats:

#jbod