Recent searches
Search options
#lvm
Völlig irrational, aber jedes mal, wenn ich ein #LVM vergrößern muss, krieg' ich schwitzige Hände. Dabei ist noch nie was schief gegangen.
Hello to #Agama 13! Packed with powerful upgrades for the #installer:
Set hostnames via #UI
Install with #LVM through the web
Enhanced support for AutoYaST URLs + unattended search
#openSUSE #Linux #YaST https://agama-project.github.io/blog/2025/04/08/agama-13
For more LVM2 recipes, see this great website by Oleg Volkov (voleg4u):
http://www.voleg.info/lvm2.html
Each time I needed to migrate my data to a new SSD with LVM and LUKS, I struggled a lot, until I figured this out properly. I have documented all necessary steps in this document:
https://gist.github.com/andrewshadura/58098ea35471f2067bf9e5a33aec0c35
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
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
@Nimbius666
WUOT ZE FUQ?
Seriously, the only use-case for a #RAID controller is to handle shitty #OS|es that can't be assed to have proper #LVM & Software-RAID integrated, like #Windows & "#WindowsServer" which IMHO have no legitimate reason to exist or be deployed newly.
#SMART varoitti tänään, että yksi #pöytäkone'en #kiintolevy (1½ Tt HDD) olisi pettämässä 24 tunnin kuluessa. Levy on kieltämättä ainakin 15 vuotta vanha, mutta ongelma oli, että a) se oli osa #LVM:ää eikä siinä ollut enää ”#extent'tejä”, joihin dataa siirtää, ja b) koneen kotelossa oli vain kaksi paikkaa 3½" kiintolevyille, kumpikin käytössä.
Ratkaisu: 5¼" paikalla oleva #bluray-asema irti ja uusi levy väliaikaisesti siihen (ruuveitta, jalustalla). Ja ei kun dataa pelastamaan! #atkjuttuja
#Persut saa taas tavoitteitaan läpi.
#LuluRanne tällä kertaa. #LVM lopettaa #ilmasto- ja ympäristöyksikön.
"Erillinen ilmasto- ja ympäristöyksikkö aloitti toimintansa vuonna 2019. Yksikön tehtävä oli vastata muun muassa siitä, että liikenne- ja viestintäjärjestelmät ovat energiatehokkaita ja vähäpäästöisiä."
#LiikenneJaViestintäministeriö #Ranne #äärioikeisto #ilmastodenialismi #ilmastokriisi #ilmastonmuutos #politiikka
Love when I go to check something and it's unresponsive. Then I look and find this:
```
user@host:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 795M 1.2M 793M 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 30G 29G 0 100% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 2.0G 182M 1.7G 10% /boot
tmpfs 795M 12K 795M 1% /run/user/1000
```
My next 15 minutes are planned out for me. Used to be 20, I had to google the lvm command format.
#linux #lvm #selfhost #diskfull
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
Ich muss es mal wieder in aller Deutlichkeit sagen:
Ich 
#Linux
Im #Notebook meiner Frau war noch eine relativ kleine #SSD. Seit einem Jahr macht sie mega viele Fotos mit dem #Smartphone und bei der letzten Sicherung auf's Notebook waren nur noch 4 GB frei.
Ich habe das mit #LUKS vollverschlüsselte #Ubuntu kurzerhand mit Linux #Bordmitteln auf eine größere SSD umgezogen:
1. alte SSD mit dd auf neue SSD 1:1 geklont
2. neue SSD ins Notebook eingebaut und Ubuntu gestartet
3. im laufenden System unbenutzten Speicherplatz mit #gparted der verschlüsselten Root-Partition hinzugefügt.
4. im laufenden System das #LVM vergrößert
5. im laufenden System das Dateisystem vergrößert
Fertig.
Effektiver Arbeitsaufwand: 5 min
Man versuche das mal mit #BigTech #Microsoft #Windows. 
#OpenSource #FOSS #digitaleSelbstbestimmung #digitaleSouveränität #Terminal
Coming from the git world, I really wish LVM had a --fork option. Basically something like lvcreate --snapshot, but in reverse. Basically I want to create a snapshot that I can also write to, but with one command. Even snapshot example shows creating the snapshot, then creating a third writable volume based on the snapshot.