Differences

This shows you the differences between two versions of the page.

--- ccgx:root_access [2019-06-22 20:46] – [Venus OS: Root Access] mvader
+++ ccgx:root_access [2020-05-28 15:49] – [Available disk space] mvader
@@ Line 10: / Line 10: @@
 ==== Hooks to install/run own code at boot ====
+Everything, except for information on /data, will be wiped after an update.
+Therefor, the trick to make changes & modifications survive an update, is to put files you need on /data, make them be (re-)installed automatically on startup. This section describes how to do that.
 If the files /data/rcS.local or /data/rc.local exists, they will be called early (rcS) and late (rc) during startup. These scripts will survive upgrades and can be used by customers to start their own custom software. Implementation details in [[https://github.com/victronenergy/meta-victronenergy/commit/2dbd16c560ff7cdf70b1d676c0616013169c7484|this commit]].
@@ Line 22: / Line 26: @@
 https://github.com/victronenergy/venus/wiki/swupdate-project
-==== Available disk space ====
+==== Partitions and available disk space ====
-See https://github.com/victronenergy/venus/wiki/machines.
+On a GX Device, there are three partitions that matter:
+  * rootfs partition one
+  * rootfs partition two
+  * the data partition
+Only one of the two rootfs partitions will be in use. When doing a firmware update, it will be installed on the other, and the subsequent reboot will reboot the device onto that other partition.
+The data partition is not touched during a firmware update, except maybe some migration scripts that run at boot.
+When doing modifications, make sure both the data partition and the rootfs do not run out of space. We don't design or test for that situation.
+With regards to the size of the data partition, thats easy to check using the ''df'' utility. But not so for the rootfs:
+After logging into a GX device, and checking the free disk space on the rootfs(! thats not the data partition), you might get a bit disappointed at first. Don't worry too much, by design there will always be only 5% of free space.
+The reason behind is that a firmware update replaces the full filesystem on the rootfs (as an image). And its then not expanded to the full available space of the partition reserved for the rootfs.
+To see the full space, run ''/opt/victronenergy/swupdate/resize2fs.sh''. It will expand the filesystem to use all of the available space.
+For actual available diskspace on our GX Devices, see https://github.com/victronenergy/venus/wiki/machines.
+To see what resize2fs.sh is doing, without having to log into your Venus OS, see it also [[https://github.com/victronenergy/meta-victronenergy/blob/master/meta-venus/recipes-support/swupdate-scripts/files/resize2fs.sh|here]].
-And see ''/opt/victronenergy/swupdate/resize2fs.sh'', as explained [[https://github.com/victronenergy/meta-victronenergy/commit/9110beead383c22523512da992e2572c176febef|in this commit]]. Source file for the script is [[https://github.com/victronenergy/meta-victronenergy/blob/master/meta-venus/recipes-support/swupdate-scripts/files/resize2fs.sh|here]].
+Note that a firmware update will replace all of the rootfs, as also explained above. Which implies that you'll need to run resize2fs.sh again after doing a firmware update.
 ==== 1. Set access level to Superuser ====