if tarballs exceed cache partition size, stuck at bootsplash
Bug #1585299 reported by
Kyle Nitzsche
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
New
|
Undecided
|
Unassigned | ||
| The Avila project |
New
|
Undecided
|
Unassigned | ||
Bug Description
For a bespoke project I have very large custom tarballs (~600MB).
When flashing the device with ubuntu-device-flash using the --custom-tarball option, I find that when the three tarballs (with other files in cache partition) exceed the cache partition size, the device on reboot is stuck at bootsplash, and there is no obvious way to recover. The only way I have found is to reflash the device with the SP Flash tool.
I worry that an OTA that is accidentally too large could break devices in the field.
| information type: | Proprietary → Public |
To post a comment you must log in.
