out of disk space needs better handling
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
snap system gives irrelevant error messages when the SD card gets out of space.
Steps to reproduce:
1. Flash and boot the ubuntu-core 16 image on dragonboard
2. Run the command df -h to list the available space on various mounted partitions
3. Using fallocate, occupy all the available space on /writable partition
4. Install some snaps to occupy the remaining space to make sure df -h output is similar to http://
5. There would be a point where, snap install and other snap commands would start failing with following error
error: cannot communicate with server: Post http://
even sudo snap remove would not work to free up the space as can be seen in above pastebin
This can be reproduced on kvm as well by following same steps above.
| Gustavo Niemeyer (niemeyer) wrote | #1 |
| Oliver Grawert (ogra) wrote | #2 |
| Gustavo Niemeyer (niemeyer) wrote | #3 |
| I Ahmad (iahmad) wrote | #4 |
| Changed in snappy: | |
| status: | New → Confirmed |
| summary: |
- out of disk space needs better handling + ubuntu-image should add the regular 5% reserved space for root when + creating filesystem for /writable |
| Launchpad Janitor (janitor) wrote Re: ubuntu-image should add the regular 5% reserved space for root when creating filesystem for /writable | #5 |
| affects: | subiquity (Ubuntu) → ubuntu-image (Ubuntu) |
| Changed in ubuntu-image (Ubuntu): | |
| status: | New → Confirmed |
| Gustavo Niemeyer (niemeyer) wrote | #6 |
| summary: |
- ubuntu-image should add the regular 5% reserved space for root when - creating filesystem for /writable + out of disk space needs better handling |
| Barry Warsaw (barry) wrote | #7 |
| no longer affects: | ubuntu-image (Ubuntu) |
| Oliver Grawert (ogra) wrote | #8 |
| Changed in snappy: | |
| importance: | Undecided → Medium |
| status: | Confirmed → Triaged |
| affects: | snappy → snapd |
It's hard to do a great job on actual out-of-space, but we should at least try to avoid getting snapd into the situation via its own means.
For that, the first step is probably to preempt better the case of space getting short, and not allow installs/refreshes while the situation isn't sorted.