bolha.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
We're a Brazilian IT Community. We love IT/DevOps/Cloud, but we also love to talk about life, the universe, and more. | Nós somos uma comunidade de TI Brasileira, gostamos de Dev/DevOps/Cloud e mais!

Server stats:

255
active users

#lvm

0 posts0 participants0 posts today

hey hey #Linux #FileSystem #ZFS #RAID #XFS entities! I'm looking for extremely opinionated discourses on alternatives to ZFS on Linux for slapping together a #JBOD ("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
#proxmox ZFS array where a raw disk image is stored for a #Qemu #VirtualMachine; in the VM, it's formatted to XFS. That "seems" fine in limited testing thus far (and seems 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
#BTRFS 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
#LVM, etc, or whatever might help me stay in tree and up to date. Thank you! Boosts appreciated and welcome.

#techPosting

Running your own AI in-house – Part 1 – LLM/LVM – Ollama in the shell

In this guide I’ll show you how to install Ollama and running your first LLM/LVM, recommend some models, give you examples on how to script with it and finally how to describe images.

This is the first article in a series of articles on how to run AI in-house.

https://www.sindastra.de/p/3373/running-your-own-ai-in-house-part-1-llm-lvm-ollama-in-the-shell

Sindastra's info dump · Running your own AI in-house – Part 1 – LLM/LVM – Ollama in the shell - Sindastra's info dump
More from Sindastra
#AI#linux#LLM

I just installed Arch manually, but now it fails to boot. It only asks to unlock nvme1n1p1, but not the root, leading to a "failed to find root" error.

fstab seems correct. I suspect the issue is in crypttab.
Does anyone know a good blog post or guide to set it up correctly? I feel like I’m close to solving this.

#ArchLinux #Btrfs #LVM #LUKS #Linux

1/2

Anybody got any experience or resources for this #linux and #LVM thing I need to do?

I have a new server I'm installing the xcp-ng hypervisor on. Right now, it has 10 disk slots, 2 for the RAID root volume, and 8 for the #LVM #RAID set. But I have this intermediate step I need to go through first and that's where I have a question.

Let's call the drives A - J. Right now A/B is a root partition mirrored pair. That's how they're gonna stay. They're small 233Gb. Drives C-J will be 8 x 2TB drives in a RAID 6 config. Right now, drives C and D are in the system in a non-redundant temporary config, holding about 5 VMs of important stuff. (Yes I have backups, no I don't want to use those backups 😃 )

What I want to do is put the additional 6 drives (E-J) in and make a RAID6 volume group. Then I'll migrate all the VMs from the non-redundant disks onto that VG. Then I'll wipefs those 2 non-redundant disks, and add them to the volume group. That gets me my 8-disk, RAID6 array.

I guess, since I don't have a ton of experience with LVM, I'm asking "is it really that easy?" Anything I should look out for?

It seems straightforward to create a RAID6 setup with only 6 disks. After I wipe disks C and D, it seems straightforward to say "Hey Volume Group, Here's some more PVs to use". But do I need to do anything more sophisticated? E.g., designating drives to have certain roles when I first create that 6-disk array? Is there something I'm not thinking about?
#selfhost #selfhosting