{"id":5000,"date":"2019-07-16T19:27:54","date_gmt":"2019-07-16T17:27:54","guid":{"rendered":"https:\/\/speefak.spdns.de\/oss_lifestyle\/?p=5000"},"modified":"2024-06-02T18:20:00","modified_gmt":"2024-06-02T16:20:00","slug":"sailfish-os-systempartition-vergroessern","status":"publish","type":"post","link":"https:\/\/speefak.spdns.de\/oss_lifestyle\/sailfish-os-systempartition-vergroessern\/","title":{"rendered":"Sailfish OS &#8211; Systempartition vergr\u00f6\u00dfern"},"content":{"rendered":"<h2>Systempartition vergr\u00f6\u00dfern<\/h2>\n<p>Standardm\u00e4\u00dfig ist die Systempartition von Sailfish OS 2,44 GB gro\u00df, wovon 1,3 GB bereits vom System belegt sind. Dies kann nach der Installation vieler Apps im Falle eines Updates zum Problem werden, da Sailfish OS f\u00fcr jedes Systemupdate ca. 650-700 MB freien Speicher voraussetzt.<\/p>\n<p>Die grundlegende Partitionsverwaltung von Sailfish OS basiert auf dem Logical Volume Manager (LVM), der eine relativ einfache Modifikation der Partitionsgr\u00f6\u00dfen erlaubt. Um die LVM Verwaltung nutzen zu k\u00f6nnen, muss das Ger\u00e4t im Recovery Modus gestartet werden. Wie der Recovertyboot und die \u00c4nderung der Partitionsgr\u00f6\u00dfen funktioniert, wird im Folgenden beschrieben:<\/p>\n<p><strong>ACHTUNG! Vollst\u00e4ndiger Datenverlust bei falscher Befehlseingabe oder der Wahl falscher Speichergr\u00f6\u00dfen!<\/strong><br \/>\n<strong>Das Ger\u00e4t selbst kann nicht besch\u00e4digt werden, Wiederherstellung der Grundsystemkonfiguration jederzeit m\u00f6glich, allerdings auch hier vollst\u00e4ndiger Datenverlust!<\/strong><\/p>\n<ol>\n<li>Ger\u00e4t im Fastboot Modus mit Rechner verbinden (Ger\u00e4t bei gedr\u00fcckter Volume Up Taste mit dem Rechner verbinden, Signal LED des Ger\u00e4tes leuchtet blau)<br \/>\nRecovery Image, falls n\u00f6tig, (in ZIP-Installationsdatei enthalten) auf das Ger\u00e4t flashen (i.d.R. kann das Recovery Image direkt \u00fcber den PC gestartet werden, s. Schritt 2) :<\/p>\n<pre class=\"lang:sh decode:true\">sudo fastboot flash recovery hybris-recovery.img<\/pre>\n<\/li>\n<li>Recovery Image via Fastboot starten (Xperia X Compact: Bildschirm des Ger\u00e4tes ist aktiv, jedoch vollkommen schwarz):\n<pre class=\"lang:sh decode:true\">sudo fastboot boot hybris-recovery.img<\/pre>\n<\/li>\n<li>Verbindung zur Recovery Konsole des Ger\u00e4tes \u00fcber Telnet aufbauen:\n<pre class=\"lang:sh decode:true\">telnet 10.42.66.66<\/pre>\n<\/li>\n<li>Xperia X* (LUKS verschl\u00fcsselt) (<a href=\"https:\/\/together.jolla.com\/question\/222126\/guide-installing-sailfish-x-on-xperias\/#222126-33-increasing-the-root-lvm-volume-size\" target=\"_blank\" rel=\"noopener\">Ausf\u00fchrliche Anleitung f\u00fcr alle Sailfish OS Systeme<\/a>) <a href=\"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-content\/uploads\/2022\/05\/Guide_Installing_Sailfish_X_on_Xperias.pdf\" target=\"_blank\" rel=\"noopener\">PDF Download<\/a>:\n<pre class=\"lang:default decode:true\"># show LVM volumes\r\nlvm lvdisplay\r\n\r\n# open LUKS container\r\ncryptsetup luksOpen \/dev\/mapper\/sailfish-home crypt-home\r\n\r\n# check filesystem and shrink home partition\r\ne2fsck -f \/dev\/mapper\/crypt-home\r\nresize2fs -f \/dev\/mapper\/crypt-home 10G\r\ne2fsck -f \/dev\/mapper\/crypt-home\r\n\r\n# shrink size of cryptsetup-container to 10,49 GiB (22000000 sectors \u00e1 512 Bytes; you might use 66000000 = 31,47 GiB on 64 GiB devices):\r\ncryptsetup resize -b 22000000 \/dev\/mapper\/sailfish-home\r\ncryptsetup close crypt-home\r\nlvm lvchange -a n sailfish\/home\r\n\r\n# Shrink \"home\" volume by -911 extents (= -3644M) for a 6 GiB, -1423 extents (= -5692M) for a 8 GiB, -399 extents (= -1596M) for a 4 GiB or -1935 extents (= -7740M) for a 10 GiB \"root\" volume size:\r\nlvm lvresize -l -911 sailfish\/home\r\n\r\n# extend LVM device root to 100% of freed space \r\nlvm lvresize -l +100%FREE sailfish\/root\r\n\r\n# open LVM home again\r\nlvm lvchange -a y sailfish\/home\r\ncryptsetup luksOpen \/dev\/mapper\/sailfish-home crypt-home\r\n\r\n\r\n# extend LVM device home \r\ncryptsetup resize \/dev\/mapper\/sailfish-home\r\nresize2fs -f \/dev\/mapper\/crypt-home\r\ne2fsck -f \/dev\/mapper\/crypt-home\r\ncryptsetup close crypt-home\r\nresize2fs \/dev\/mapper\/sailfish-root\r\n\r\n# show LVM volumes\r\nlvm lvdisplay\r\n<\/pre>\n<\/li>\n<li>Xperia X* (keine LUKS verschl\u00fcsselung) (bis SFOS Version 3.3) =&gt; Shell\/Konsole starten und Partitionen bearbeiten (Systempartition auf 4 GB vergr\u00f6\u00dfern) :\n<pre class=\"lang:sh decode:true\">e2fsck -f \/dev\/sailfish\/home # ( use \"4) Perform file system check\" for encrypted devices )\r\nlvm pvs\t\t\t\t\t\t\t\r\nlvm lvs\t\t\t\t\t\t\r\nresize2fs \/dev\/sailfish\/home 15G\r\nlvm lvextend --size 4G  \/dev\/sailfish\/root\r\nlvm lvresize -l +100%FREE \/dev\/sailfish\/home\r\nresize2fs \/dev\/sailfish\/home\t\t\t\t\t\r\nresize2fs \/dev\/sailfish\/root\r\ne2fsck -f \/dev\/sailfish\/homedf -h\t\t\t\t\r\nlvm lvs<\/pre>\n<p>* lvm lvextend &#8211;size 5G \/dev\/sailfish\/root vergr\u00f6\u00dfert die Systempartition auf 5 GB. Bei gr\u00f6\u00dferen Werten (&lt; 6 GB) muss die Home Partition und der Home LV st\u00e4rker reduziert werden.<\/li>\n<\/ol>\n<ol>\n<li>Das Ganze sieht dann wie folgt aus ( SFOS 4.4 @ XA2 , LUKS verschl\u00fcsselt )\n<pre class=\"height-set:true lang:default decode:true\">-----------------------------\r\n     Jolla Recovery v2.0\r\n-----------------------------\r\nWelcome to the recovery tool!\r\nThe available options are:\r\n1) Reset device to factory state\r\n2) Reboot device\r\n3) Shell\r\n4) Perform file system check\r\n5) Run sshd\r\n6) Exit\r\nType the number of the desired action and press [Enter]: \r\n3\r\n\r\nIf you continue, this may void your warranty. Are you really SURE? [y\/N] y\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input\/output error\r\n  2 logical volume(s) in volume group \"sailfish\" now active\r\nSat May 21 14:44:30 UTC 2022\r\n\r\n\r\nType your devicelock code and press [ENTER] key:\r\n(please note that the typed numbers won't be shown for security reasons)\r\n[OK] Code accepted.\r\n\/ #  cryptsetup luksOpen \/dev\/mapper\/sailfish-home crypt-home\r\nEnter passphrase for \/dev\/mapper\/sailfish-home: \r\n\/ # e2fsck -f \/dev\/mapper\/crypt-home\r\ne2fsck 1.45.4 (23-Sep-2019)\r\nPass 1: Checking inodes, blocks, and sizes\r\nPass 2: Checking directory structure\r\nPass 3: Checking directory connectivity\r\nPass 4: Checking reference counts\r\nPass 5: Checking group summary information\r\n\/dev\/mapper\/crypt-home: 1411\/1150560 files (3.5% non-contiguous), 155108\/4601344 blocks\r\n\/ # resize2fs -f \/dev\/mapper\/crypt-home 10G\r\nresize2fs 1.45.4 (23-Sep-2019)\r\nResizing the filesystem on \/dev\/mapper\/crypt-home to 2621440 (4k) blocks.\r\nThe filesystem on \/dev\/mapper\/crypt-home is now 2621440 (4k) blocks long.\r\n\r\n\/ # e2fsck -f \/dev\/mapper\/crypt-home\r\ne2fsck 1.45.4 (23-Sep-2019)\r\nPass 1: Checking inodes, blocks, and sizes\r\nPass 2: Checking directory structure\r\nPass 3: Checking directory connectivity\r\nPass 4: Checking reference counts\r\nPass 5: Checking group summary information\r\n\/dev\/mapper\/crypt-home: 1411\/652800 files (3.5% non-contiguous), 121811\/2621440 blocks\r\n\/ # cryptsetup resize -b 22000000 \/dev\/mapper\/sailfish-home\r\n\/ # cryptsetup close crypt-home\r\n\/ # lvm lvchange -a n sailfish\/home\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n\/ # lvm lvresize -l -911 sailfish\/home\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  Size of logical volume sailfish\/home changed from 17.55 GiB (4494 extents) to &lt;14.00 GiB (3583 extents).\r\n  Logical volume sailfish\/home successfully resized.\r\n\/ # lvm lvresize -l +100%FREE sailfish\/root\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  Size of logical volume sailfish\/root changed from 2.44 GiB (625 extents) to 6.00 GiB (1536 extents).\r\n  Logical volume sailfish\/root successfully resized.\r\n\/ # lvm lvchange -a y sailfish\/home\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n\/ # lvm lvresize -l +100%FREE sailfish\/root\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  New size (1536 extents) matches existing size (1536 extents).\r\n\/ # lvm lvchange -a y sailfish\/home\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n\/ # cryptsetup luksOpen \/dev\/mapper\/sailfish-home crypt-home\r\nEnter passphrase for \/dev\/mapper\/sailfish-home: \r\n\/ # cryptsetup resize \/dev\/mapper\/sailfish-home\r\n\/ # resize2fs -f \/dev\/mapper\/crypt-home\r\nresize2fs 1.45.4 (23-Sep-2019)\r\nResizing the filesystem on \/dev\/mapper\/crypt-home to 3668480 (4k) blocks.\r\nThe filesystem on \/dev\/mapper\/crypt-home is now 3668480 (4k) blocks long.\r\n\r\n\/ # e2fsck -f \/dev\/mapper\/crypt-home\r\ne2fsck 1.45.4 (23-Sep-2019)\r\nPass 1: Checking inodes, blocks, and sizes\r\nPass 2: Checking directory structure\r\nPass 3: Checking directory connectivity\r\nPass 4: Checking reference counts\r\nPass 5: Checking group summary information\r\n\/dev\/mapper\/crypt-home: 1411\/913920 files (3.5% non-contiguous), 139222\/3668480 blocks\r\n\/ # cryptsetup close crypt-home\r\n\/ # resize2fs \/dev\/mapper\/sailfish-root\r\nresize2fs 1.45.4 (23-Sep-2019)\r\nFilesystem at \/dev\/mapper\/sailfish-root is mounted on \/rootfs; on-line resizing required\r\nold_desc_blocks = 1, new_desc_blocks = 1\r\nThe filesystem on \/dev\/mapper\/sailfish-root is now 1572864 (4k) blocks long.\r\n\r\n\/ # lvm lvdisplay\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  --- Logical volume ---\r\n  LV Path                \/dev\/sailfish\/root\r\n  LV Name                root\r\n  VG Name                sailfish\r\n  LV UUID                By9QbR-6CTe-NONJ-637d-yPcT-yckB-04ljMe\r\n  LV Write Access        read\/write\r\n  LV Creation host, time SailfishSDK, 2022-05-11 11:25:03 +0000\r\n  LV Status              available\r\n  # open                 1\r\n  LV Size                6.00 GiB\r\n  Current LE             1536\r\n  Segments               3\r\n  Allocation             inherit\r\n  Read ahead sectors     auto\r\n  - currently set to     256\r\n  Block device           252:0\r\n   \r\n  --- Logical volume ---\r\n  LV Path                \/dev\/sailfish\/home\r\n  LV Name                home\r\n  VG Name                sailfish\r\n  LV UUID                ztMtfR-x5qh-0scX-CmKK-tIoB-QB3z-TkaKDr\r\n  LV Write Access        read\/write\r\n  LV Creation host, time SailfishSDK, 2022-05-11 11:25:03 +0000\r\n  LV Status              available\r\n  # open                 0\r\n  LV Size                &lt;14.00 GiB\r\n  Current LE             3583\r\n  Segments               2\r\n  Allocation             inherit\r\n  Read ahead sectors     auto\r\n  - currently set to     256\r\n  Block device           252:1\r\n   \r\n\/ # exit\r\n-----------------------------\r\n     Jolla Recovery v2.0\r\n-----------------------------\r\nWelcome to the recovery tool!\r\nThe available options are:\r\n1) Reset device to factory state\r\n2) Reboot device\r\n3) Shell\r\n4) Perform file system check\r\n5) Run sshd\r\n6) Exit\r\nType the number of the desired action and press [Enter]: \r\n2\r\nRebooting...<\/pre>\n<p>Xperia X Compact , unverschl\u00fcsselt :<\/p>\n<pre class=\"height-set:true lang:sh decode:true\">Welcome to the recovery tool!\r\nThe available options are:\r\n1) Reset device to factory state\r\n2) Reboot device\r\n3) Shell\r\n4) Perform file system check\r\n5) Run sshd\r\n6) Exit\r\nType the number of the desired action and press [Enter]: \r\n4\r\n\/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n2 logical volume(s) in volume group \"sailfish\" now active\r\ne2fsck 1.45.4 (23-Sep-2019)\r\nPass 1: Checking inodes, blocks, and sizes\r\nPass 2: Checking directory structure\r\nPass 3: Checking directory connectivity\r\nPass 4: Checking reference counts\r\nPass 5: Checking group summary information\r\nroot: 27418\/153600 files (0.4% non-contiguous), 377279\/640000 blocks\r\nOpening encrypted filesystem, you will be prompted for your security code.\r\nEnter passphrase for \/dev\/sailfish\/home: \r\ne2fsck 1.45.4 (23-Sep-2019)\r\nPass 1: Checking inodes, blocks, and sizes\r\nPass 2: Checking directory structure\r\nPass 3: Checking directory connectivity\r\nPass 4: Checking reference counts\r\nPass 5: Checking group summary information\r\n\/dev\/mapper\/luks-home: 1322\/1150560 files (3.5% non-contiguous), 159719\/4601344 blocks\r\n\/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n0 logical volume(s) in volume group \"sailfish\" now active\r\nDone\r\nPress [Enter] to return to recovery menu...\r\n-----------------------------\r\n     Jolla Recovery v2.0\r\n-----------------------------\r\nWelcome to the recovery tool!\r\nThe available options are:\r\n1) Reset device to factory state\r\n2) Reboot device\r\n3) Shell\r\n4) Perform file system check\r\n5) Run sshd\r\n6) Exit\r\nType the number of the desired action and press [Enter]: \r\n3\r\n\r\nIf you continue, this may void your warranty. Are you really SURE? [y\/N] [y\/N] y\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input\/output error\r\n  2 logical volume(s) in volume group \"sailfish\" now active\r\n[OK] No lockcode has been set. Proceeding...\r\n\/ # lvm pvs\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input\/output error\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input\/output error\r\n  PV              VG       Fmt  Attr PSize  PFree\r\n\/ # lvm vgs\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  VG       #PV #LV #SN Attr   VSize  VFree\r\n  sailfish   1   2   0 wz--n- 22.25g    0  \r\n\/ # lvm lvs\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  LV   VG       Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert\r\n  home sailfish -wi-a----- &lt;19.81g                                                    \r\n  root sailfish -wi-ao----   2.44g                                                    \r\n\/ # resize2fs \/dev\/sailfish\/home 15G\r\nresize2fs 1.45.0 (6-Mar-2019)\r\nResizing the filesystem on \/dev\/sailfish\/home to 3932160 (4k) blocks.\r\nThe filesystem on \/dev\/sailfish\/home is now 3932160 (4k) blocks long.\r\n\/ # lvm lvresize -L -4563M \/dev\/sailfish\/home\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  Rounding size to boundary between physical extents: 4.45 GiB.\r\n  WARNING: Reducing active logical volume to &lt;15.36 GiB.\r\n  THIS MAY DESTROY YOUR DATA (filesystem etc.)\r\nDo you really want to reduce sailfish\/home? [y\/n]: y\r\n  Size of logical volume sailfish\/home changed from &lt;19.81 GiB (5071 extents) to &lt;15.36 GiB (3931 extents).\r\n  Logical volume sailfish\/home successfully resized.\r\n\/ # lvm lvs\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  LV   VG       Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert\r\n  home sailfish -wi-a----- &lt;15.36g                                                    \r\n  root sailfish -wi-ao----   2.44g                                                    \r\n\/ # lvm vgs\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  VG       #PV #LV #SN Attr   VSize  VFree\r\n  sailfish   1   2   0 wz--n- 22.25g 4.45g\r\n\/ # lvm lvextend --size 4G  \/dev\/sailfish\/root\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  Size of logical volume sailfish\/root changed from 2.44 GiB (625 extents) to 4.00 GiB (1024 extents).\r\n  Logical volume sailfish\/root successfully resized.\r\n\/ # lvm lvresize -l +100%FREE \/dev\/sailfish\/home\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  Size of logical volume sailfish\/home changed from &lt;15.36 GiB (3931 extents) to 18.25 GiB (4672 extents).\r\n  Logical volume sailfish\/home successfully resized.\r\n\/ # lvm lvs\r\n  \/dev\/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input\/output error\r\n  LV   VG       Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert\r\n  home sailfish -wi-a----- 18.25g                                                    \r\n  root sailfish -wi-ao----  4.00g                                                    \r\n\/ # resize2fs \/dev\/sailfish\/home\r\nresize2fs 1.45.0 (6-Mar-2019)\r\nResizing the filesystem on \/dev\/sailfish\/home to 4784128 (4k) blocks.\r\nThe filesystem on \/dev\/sailfish\/home is now 4784128 (4k) blocks long.\r\n\/ # resize2fs \/dev\/sailfish\/root\r\nresize2fs 1.45.0 (6-Mar-2019)\r\nFilesystem at \/dev\/sailfish\/root is mounted on \/rootfs; on-line resizing required\r\nold_desc_blocks = 1, new_desc_blocks = 1\r\nThe filesystem on \/dev\/sailfish\/root is now 1048576 (4k) blocks long.\r\n\r\n<\/pre>\n<\/li>\n<\/ol>\n<h2>Detaillierte Erl\u00e4uterung des o.g. Vorgehens<\/h2>\n<p>Logical Volume Manager (LVM) basierende Systeme sind in zwei Schichten aufgebaut, die alle innerhalb eines Containers (Physical Volume (PV)) liegen. Die PVs enthalten die Logischen Volumes (LV) die wiederum die Dateisysteme enthalten auf denen letztendlich die Daten gespeichert werden.<\/p>\n<p>Um \u00c4nderungen an den LVM Volumes und Dateisystemen durchzuf\u00fchren muss man daher in umgekehrter Reihenfolge verfahren. Um z.b. die Dateisysteme\/Partitionen, die sich in den LVs befinden, zu \u00e4ndern m\u00fcssen die Dateisysteme zuerst verkleinert werden damit dann die Logischen Volumes ge\u00e4ndert werden k\u00f6nnen.<\/p>\n<p>Ein frisch geflashtes Sailfish OS Ger\u00e4t hat per Default folgende Speicheraufteilung:<br \/>\n<span style=\"font-size: 8pt;\">(ab SFOS Gen. 2 Xperia X | Gen 1 hat keine Aufteilung zwischen System und Userdaten )<\/span><\/p>\n<p><span style=\"font-family: courier new, courier, monospace;\">| \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 PV auf gesamter Festplatte 22.25 GB \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| LV1 2.44GB |\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 LV2 19.81GB \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| FS1 2.44GB | \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0\u00a0 FS2 19.81GB \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 |<\/span><\/p>\n<p>Um FS1 auf LV1 um 2 GB auf 4 GB zu vergr\u00f6\u00dfern muss dazu LV2 um 2GB verkleinert werden, da das PV den gesamten physikalischen speicher (gesamte Festplatte) bereits nutzt. W\u00fcrde man einfach die logischen Volumes bearbeiten stimmen die Gr\u00f6\u00dfen nicht mehr mit den darauf enthalten Dateisystemen \u00fcberein und es kommt zu Dateisystem Fehlern und Datenverlust. Darum m\u00fcssen zu erst die Dateisysteme selbst bearbeitet werden, i o.g. Fall muss das Dateisystem FS2 mindestens um 2 GB verkleinert werden.<\/p>\n<p>Als Erstes wird FS2 auf 15 GB reduziert. Dabei enstehen im LV2 4,81 GB freier Speicher.<\/p>\n<p><span style=\"font-family: courier new, courier, monospace;\">|<\/span><span style=\"font-family: courier new, courier, monospace;\"> \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 PV auf gesamter Festplatte 22.25 GB \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| LV1 2.44GB |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 LV2 19.81GB\u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| FS1 2.44GB |\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0\u00a0\u00a0 LV2 4,81GB frei\u00a0 | FS2 15.00GB |<\/span><\/p>\n<p>Nachdem FS2 reduziert wurde kann jetzt LV2 reduziert werden. Zur Sicherheit sollte dabei ein Puffer ber\u00fccksichtigt werden (0.36 GB).<\/p>\n<p><span style=\"font-family: courier new, courier, monospace;\">| \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 PV auf gesamter Festplatte 22.25 GB \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| LV1 2.44GB | \u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PV 4.45GB frei <\/span><span style=\"font-family: courier new, courier, monospace;\">|\u00a0 \u00a0 \u00a0\u00a0 \u00a0 LV2 15.36GB \u00a0 \u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| FS1 2.44GB |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | LV2 0.36GB frei | FS2 15.00GB |<\/span><\/p>\n<p>Der jetzt freie Speicher im PV kann nun den LVs zugewiesen werden. In diesem Fall wird LV1 auf 4GB vergr\u00f6\u00dfert. In diesem Beispiel w\u00e4re eine maximale Vergr\u00f6\u00dferung von LV1 auf 6,89 GB (2,44GB + 4,45 GB) m\u00f6glich.<\/p>\n<p><span style=\"font-family: courier new, courier, monospace;\">| \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 PV auf gesamter Festplatte 22.25 GB \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| LV1 4.00GB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | PV 2,89GB frei | \u00a0\u00a0 \u00a0 \u00a0\u00a0 LV2 15.36GB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| FS1 2.44GB | LV1 1.56 frei |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | LV2 0.36GB frei | FS2 15.00GB |<br \/>\n<\/span><\/p>\n<p>Da LV1 nur auf 4 GB vergr\u00f6\u00dfert wurde, und somit 2,89 GB im PV ungenutzt sind, wird der \u00fcbrig gebliebene Speicher des PV jetzt wieder dem LV2 zugewiesen. Die Zuweisung kann auch direkt ohne den Zwischenschritt der Puffer durchgef\u00fchrt werden, erfordert dabei aber genaue Berechnung der FS Extends und den FS Gr\u00f6\u00dfen. Es ist jedoch einfacher den Ziel LV (LV1) mit einer direkten Gr\u00f6\u00dfenagabe zu \u00e4ndern und den nachfolgen LV (LV2) mit automatisch erfolger Speicherplatzberechnung wieder zu maximieren.<\/p>\n<p><span style=\"font-family: courier new, courier, monospace;\">| \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 PV auf gesamter Festplatte 22.25 GB \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| LV1 4.00GB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0 LV2 18,25GB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">| FS1 2.44GB | LV1 1.56 frei |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 LV2 3,25GB frei | FS2 15.00GB |<\/span><\/p>\n<p>Nach Abschluss der \u00c4nderungen an den LVs muss jetzt noch das Dateisystem an die neuen Gr\u00f6\u00dfen der LVs angepasst werden<\/p>\n<p><span style=\"font-family: courier new, courier, monospace;\">| \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 PV auf gesamter Festplatte 22.25 GB \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">|\u00a0 \u00a0\u00a0 \u00a0 LV1 4.00GB\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0 LV2 18,25GB \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/span><br \/>\n<span style=\"font-family: courier new, courier, monospace;\">|\u00a0\u00a0 \u00a0 \u00a0 FS1 4.00GB \u00a0\u00a0\u00a0 \u00a0 | \u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 FS2 15.00GB\u00a0\u00a0\u00a0\u00a0 \u00a0\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0\u00a0 |<\/span><\/p>\n<hr \/>\n<p><span style=\"font-size: 8pt;\"><img loading=\"lazy\" decoding=\"async\" class=\" wp-image-2821 alignleft\" src=\"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-content\/uploads\/2014\/08\/CC_BY_NC_SA.png\" alt=\"CC_BY_NC_SA\" width=\"65\" height=\"23\" \/><span style=\"font-size: 10pt;\">by Speefak<\/span> | <a href=\"https:\/\/together.jolla.com\/question\/156279\/installing-system-updates-fails-when-there-is-not-enough-space-in-system-data-partition\/?answer=156670#post-id-156670\" target=\"_blank\" rel=\"noopener noreferrer\">together.jolla.com<\/a> | <a href=\"https:\/\/together.jolla.com\/question\/200683\/sailfishx-gemini-the-rootfs-is-too-small\/\">together.jolla.com<\/a> | <a href=\"https:\/\/blog.pcfe.net\/hugo\/posts\/2019-03-03-sailfish-shrink-home\/\">blog.pcfe.net<\/a> | <a href=\"https:\/\/www.tecmint.com\/manage-and-create-lvm-parition-using-vgcreate-lvcreate-and-lvextend\/\">www.tecmint.com<\/a>| <\/span><a href=\"https:\/\/www.getwox.com\/fastboot-commands\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-size: 8pt;\">Fastboot Befehle<\/span><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Systempartition vergr\u00f6\u00dfern Standardm\u00e4\u00dfig ist die Systempartition von Sailfish OS 2,44 GB gro\u00df, wovon 1,3 GB bereits vom System belegt sind. Dies kann nach der Installation vieler Apps im Falle eines Updates zum Problem werden, da Sailfish OS f\u00fcr jedes Systemupdate ca. 650-700 MB freien Speicher voraussetzt. Die grundlegende Partitionsverwaltung von Sailfish OS basiert auf dem [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,26,37],"tags":[],"class_list":["post-5000","post","type-post","status-publish","format-standard","hentry","category-anleitungen","category-linux","category-sailfish-os"],"rttpg_featured_image_url":null,"rttpg_author":{"display_name":"speefak","author_link":"https:\/\/speefak.spdns.de\/oss_lifestyle\/author\/speefak_oss\/"},"rttpg_comment":0,"rttpg_category":"<a href=\"https:\/\/speefak.spdns.de\/oss_lifestyle\/category\/anleitungen\/\" rel=\"category tag\">Anleitungen<\/a> <a href=\"https:\/\/speefak.spdns.de\/oss_lifestyle\/category\/linux\/\" rel=\"category tag\">Linux<\/a> <a href=\"https:\/\/speefak.spdns.de\/oss_lifestyle\/category\/sailfish-os\/\" rel=\"category tag\">Sailfish OS<\/a>","rttpg_excerpt":"Systempartition vergr\u00f6\u00dfern Standardm\u00e4\u00dfig ist die Systempartition von Sailfish OS 2,44 GB gro\u00df, wovon 1,3 GB bereits vom System belegt sind. Dies kann nach der Installation vieler Apps im Falle eines Updates zum Problem werden, da Sailfish OS f\u00fcr jedes Systemupdate ca. 650-700 MB freien Speicher voraussetzt. Die grundlegende Partitionsverwaltung von Sailfish OS basiert auf dem&hellip;","_links":{"self":[{"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/posts\/5000","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/comments?post=5000"}],"version-history":[{"count":0,"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/posts\/5000\/revisions"}],"wp:attachment":[{"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/media?parent=5000"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/categories?post=5000"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/speefak.spdns.de\/oss_lifestyle\/wp-json\/wp\/v2\/tags?post=5000"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}