MGOS_ROOT_FS_SIZE and OTA upgrade

General
1

If I change MGOS_ROOT_FS_SIZE between factory released version of software and an OTA upgrade, does the OTA upgrade fail or brick the device?

In other words, does the OTA lib successfully handle different rootfs size between OTA versions?

2

Why not trying that out?

3

Compiled with fs = 256kB (262144 bytes), and OTA with fs = 448 kB (458752 bytes). From a smaller fs to a larger fs.

Portions of the log:

[Jun 20 20:52:51.997] I (45) boot: Partition Table:
[Jun 20 20:52:51.997] I (47) boot: ## Label            Usage          Type ST Offset   Length   Flags
[Jun 20 20:52:52.010] I (54) boot:  0 nvs              WiFi data        01 02 00009000 00004000 00000000
[Jun 20 20:52:52.011] I (61) boot:  1 otadata          OTA data         01 00 0000d000 00002000 00000000
[Jun 20 20:52:52.029] I (69) boot:  2 app_0            OTA app          00 10 00010000 00180000 00000000
[Jun 20 20:52:52.029] I (76) boot:  3 fs_0             SPIFFS           01 82 00190000 00040000 00000000
[Jun 20 20:52:52.044] I (83) boot:  4 app_1            OTA app          00 11 001d0000 00180000 00000000
[Jun 20 20:52:52.045] I (91) boot:  5 fs_1             SPIFFS           01 82 00350000 00040000 00000000
[Jun 20 20:52:52.051] I (98) boot: End of partition table
[Jun 20 20:52:52.061] I (101) boot: OTA data 0: seq 0x00000001, st 0x10, CRC 0x157a2b85, valid? 1
[Jun 20 20:52:52.062] I (108) boot: OTA data 1: seq 0x00000000, st 0x00, CRC 0x00000000, valid? 0

[Jun 20 20:53:00.946] mgos_ota_core.c:253     Starting, timeout 60, commit timeout 30, mem 4334408
[Jun 20 20:53:00.962] mgos_ota_core.c:489     FW: xxxxxxx esp32 1.5.0 20190621-000223/XXXX-1.5.0-2-g9907f0a-master
[Jun 20 20:53:04.850] esp32_ota_backend.c:344 Write 512 @ 262144 failed: 260
[Jun 20 20:53:04.867] mgos_ota_core.c:811     Update finished, result -1 (Failed to write data)
[Jun 20 20:54:00.937] mgos_ota_http_clien:270 Update URL: https://xxxxxxxx/xxxxxx-esp32-1.5.0.zip
[Jun 20 20:54:03.599] mgos_ota_core.c:253     Starting, timeout 60, commit timeout 30, mem 4333940
[Jun 20 20:54:03.615] mgos_ota_core.c:489     FW: xxxxxxx esp32 1.5.0 20190621-000223/XXXX-1.5.0-2-g9907f0a-master
[Jun 20 20:54:03.631] esp32_ota_backend.c:197 App: xxxx.bin -> app_1, FS: fs.img -> fs_1
[Jun 20 20:54:03.634] mgos_ota_core.c:506     0.11% total, bootloader.bin 512 of 24208
[Jun 20 20:54:03.855] esp32_ota_backend.c:219 Error reading fs_1 at offset 262144: 260
[Jun 20 20:54:03.856] esp32_ota_backend.c:288 Writing FS image @ 0x350000
[Jun 20 20:54:04.607] mgos_ota_core.c:506     1.51% total, fs.img 512 of 458752
[Jun 20 20:54:07.727] esp32_ota_backend.c:344 Write 512 @ 262144 failed: 260
[Jun 20 20:54:07.728] mgos_ota_core.c:811     Update finished, result -1 (Failed to write data)

Looks like going from smaller fs to bigger fs is not supported.