Increasing paritions size of production mender clients

General Discussions
5

Hi @genedupre.

The size is part of the format we use for delivering the updates (i.e., Mender-Artifact).

Here is an example output from one I created with mender-convert:

mender-artifact git:(mendersoftware/master) ✗ mender-artifact read *.mender
Mender artifact:
  Name: dump
  Format: mender
  Version: 3
  Signature: no signature
  Compatible devices: '[raspberrypi]'
  Provides group: 
  Depends on one of artifact(s): []
  Depends on one of group(s): []
  State scripts:

Updates:
    0:
    Type:   rootfs-image
    Provides:
	rootfs_image_checksum: aab96150f7dc51b4c9a8015dd155d7221bd965464ed212e2d71e2e96c02de721
    Depends: Nothing
    Metadata: Nothing
    Files:
      name:     rootfs.tmp187950712
      size:     513
      modified: 2020-02-12 14:36:42 +0100 CET
      checksum: aab96150f7dc51b4c9a8015dd155d7221bd965464ed212e2d71e2e96c02de721

As far as I know, there is no size-checks on the backend side, so a bigger update can be pushed in a later installment. The client will accept the update, and then fail, when it discovers that the size of the update is larger than the partition is writes to.

This is the error message you should be encountering in this case:

update (%v bytes) is larger than the size of device %s (%v bytes)

I hope this answers your question
-Ole

1 Like