Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen der Seite angezeigt.

--- content:serverbasics [2025/07/26 22:00] – obel1x
+++ content:serverbasics [2026/04/10 10:18] (aktuell) – [Mountoptions] obel1x
@@ Zeile 215: / Zeile 215: @@
 ==== LVM ====
-LVM is a powerful partition-management-layer and should always be used, when there is some none low-end hardware present. If you can use the **KDE Partitioning- Tool**  (which means having Plasma=KDE Desktop compatible support), the support is very inuitive and opens a lot of flexibility whne handling partitions, like adding more disk space or moving partitions, but also on console this offers good functionality. OpenSuSE offer to create LVM- Styled system setup in installation optionally (not by default). If you can: use it.
+LVM is a powerful partition-management-layer and should always be used, when there is some none low-end hardware present. If you can use the **KDE Partitioning- Tool** (which means having Plasma=KDE Desktop compatible support), the support is very inuitive and opens a lot of flexibility whne handling partitions, like adding more disk space or moving partitions, but also on console this offers good functionality. OpenSuSE offer to create LVM- Styled system setup in installation optionally (not by default). If you can: use it.
 === Mirror- Raided LVM- Volumes (RAID1) ===
@@ Zeile 318: / Zeile 317: @@
 </code>
+=== LVM Error Recovery ===
+In case on Harddrive is failing, the Array gets degraded. If you boot your system without that disk, it will not start due to inaktive volume groups.
+To recover, do this:
+. Get Volume Groups up, if degraded
+vgchange -a y
+. Add a new PV to the VG that is large enough to hold the Data
+vgextend vgname /dev/sdX
+. Repair the logical volume by searching for usable PVs automagically
+lvconvert –repair vgname/lvname
+This should rebuild your logical Volume
+. After rebuild, remove the faild drive from the vg:
+vgreduce –removemissing vgdata
+Thats it, your System should become usable after that.
+== Moving Data before Drive fails ==
+If you have the possibility to add a new PV before the array gets degraded, you can use the replace- method after adding the new pv to the VG:
+lvconvert –replace /dev/sdX1 vgname/lvname /dev/sdY1
+=== More Info for LVMs ===
+https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html/configuring_and_managing_logical_volumes/configuring-raid-logical-volumes_configuring-and-managing-logical-volumes
 ==== Filesystem ====
@@ Zeile 333: / Zeile 369: @@
 While autodefrag should not be necessary on ssd- harddiscs.
-For **Databases**  or files that need speed and __**are well backed up otherwise**__  : nodatacow,nodatasum,noatime,nodiratime
+For **Databases** or files that need speed and __**are well backed up otherwise**__  : nodatacow,nodatasum,noatime,nodiratime
 === Sources: ===
   * [[https://fedoraproject.org/wiki/Changes/BtrfsTransparentCompression|https://fedoraproject.org/wiki/Changes/BtrfsTransparentCompression]]
   * [[https://btrfs.readthedocs.io/en/latest/Administration.html|https://btrfs.readthedocs.io/en/latest/Administration.html]]
+=== Powermode settings ===
+Your Harddrives may have set a power level, that allows spindown. I personally would not let your harddrives spindown, because every start brings your harddrives mechanics nearer to death. In Fact there is not very much worse than spinning up and down every few minutes for a harddrive with physical discs.
+To change that, create the following file:
+<file>
+pcserver2023:/usr/lib/udev/rules.d # cat 85-hdparm.rules
+ACTION=="add|change", SUBSYSTEM=="block", KERNEL=="[sh]d[a-z]", RUN+="/sbin/hdparm -S 0 -B 128 /dev/%k"
+</file>
+That way, your harddrives will stay up all time.
 ===== Quotas =====