do-release-upgrade failure leaves a btrfs snapshot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
1. do-release-upgrade should at least notify upon failure that there is a snapshot, and ideally explain the options (delete versus rollback).
2. There should be a command line parameter to make do-release-upgrade not snapshot even if the filesystem supports it.
Ironically, the failure was due to the snapshot using ~8 GiB and causing the root filesystem to run out of free space.
There had been notification of the snapshot earlier in the upgrade process ... immediately after the download completed, i.e. at the point when one is no longer supposed to interrupt the process. When do-release-upgrade failed however, there was no notification that this snapshot still existed:
Upgrading
Inhibiting until Ctrl+C is pressed...
Create a snapshot of '/tmp/apt-
[many lines of apt output here]
Installing new version of config file /etc/usb_
dpkg: unrecoverable fatal error, aborting:
unable to install updated status of 'usb-modeswitch': No space left on device
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
To continue please press [ENTER]
Because do-release-upgrade had cleaned up that mount in /tmp, manual cleanup had to involve re-mounting. To wit:
# mount -t btrfs /dev/sda1 /mnt
# btrfs subvolume delete /mnt/@apt-
Delete subvolume (no-commit): '/mnt/@
# dpkg -a --configure
[plus some manual fixes]
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-
ProcVersionSign
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Fri Oct 13 10:55:15 2017
InstallationDate: Installed on 2016-12-02 (314 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitec
SourcePackage: ubuntu-
UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)
tags: | added: zesty2artful |
Status changed to 'Confirmed' because the bug affects multiple users.