Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung Nächste ÜberarbeitungBeide Seiten der Revision | ||
content:serverbasics [2023/07/10 16:24] – [Mountpoints] Daniel | content:serverbasics [2023/07/24 12:30] – [Raided LVM- Volumes] Daniel | ||
---|---|---|---|
Zeile 15: | Zeile 15: | ||
</ | </ | ||
+ | |||
+ | The important part is metadata=1.0 - this format has especially designed to fit the needs of raid1 of fat/efi- systems. | ||
Zeile 20: | Zeile 22: | ||
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. | ||
+ | === Raided LVM- Volumes === | ||
+ | |||
+ | Noadays, raid1 or raid5 for system without LVM is outdated. Those things are integrated in LVM - so use it! | ||
+ | |||
+ | First, creat a volume group with two same size partitions on two discs, than create a raid1 on it (for example): | ||
+ | |||
+ | < | ||
+ | vgcreate vgsystem /dev/sdX1 /dev/sdY1 | ||
+ | lvcreate -m1 --type raid1 -l 100%FREE -n lvroot vgsystem | ||
+ | |||
+ | </ | ||
+ | |||
+ | where 100%FREE means 100% of Free Space used… | ||
+ | |||
+ | To check if raid1 works, use: | ||
+ | |||
+ | < | ||
+ | lvs -a -o name, | ||
+ | |||
+ | </ | ||
+ | |||
+ | If this has not worked, use: | ||
+ | |||
+ | < | ||
+ | lvconvert --type raid1 -m1 vg_xxx/ | ||
+ | |||
+ | </ | ||
+ | |||
+ | Or - you can do raid5 with: | ||
+ | |||
+ | < | ||
+ | lvcreate -n lvdata --type raid5 -l 100%FREE -i 2 vgdata | ||
+ | |||
+ | </ | ||
+ | |||
+ | where i equals the number of devices with Data (not including parity- storage) | ||
+ | |||
+ | |||
=== Useful Commands === | === Useful Commands === | ||
Zeile 55: | Zeile 95: | ||
BTRFs has a lot of Mountoptions and some here are really odd ones for every linux. I would suggest at least those: | BTRFs has a lot of Mountoptions and some here are really odd ones for every linux. I would suggest at least those: | ||
- | For **Desktopusage**: | + | For **Desktopusage**: |
While autodefrag should not be necessary on ssd- harddiscs. | While autodefrag should not be necessary on ssd- harddiscs. | ||
For **Databases** or files that need speed and __**are well backed up otherwise**__ | For **Databases** or files that need speed and __**are well backed up otherwise**__ | ||
+ | |||
+ | |||
=== Sources: === | === Sources: === | ||