Bug #16312

Enabling persistence in Buster leads to issues at shutdown

Added by CyrilBrulebois 2019-01-06 15:15:52 . Updated 2019-04-05 09:32:29 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_4.0
Start date:
2019-01-06
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Seen with the first scenario of persistence.feature: once the test suite has been patched enough that persistence gets successfully enabled, the shutdown step contains many errors, even if it manages to stop the machine in the end.

  • Screenshot 1: initial error messages popping up.
  • Screenshot 2: example of systemd units going haywire before finally timing out.
  • Screenshot 3: last display before black screen; many units are stopped between the second and third screenshots.

I’m reproducing (parts of) the initial & final messages below to make this ticket searchable:

print_req_error: I/O error, dev sr0
print_req_error: I/O error, dev loop0
SQUASHFS error: squashfs_read_data failed to read block
SQUASHFS error: Unable to read data cache entry
SQUASHFS error: Unable to read page, block
SQUASHFS error: Unable to read fragment cache entry

[…]

[FAILED] Failed unmounting /lib/live/mount/overlay.
[FAILED] Failed unmounting /lib/live/mount/medium.
[FAILED] Failed unmounting /lib/live/mount/rootfs/filesystem.squashfs.

[…]

Failed to unmount /lib/live/mount/overlay: Device or resource busy
Failed to unmount /lib/live/mount/rootfs/filesystem.squashfs: Device or resource busy
Failed to unmount /lib/live/mount/medium: Device or resource busy

Files

tails-persistence-shutdown-errors-1.png (46933 B) CyrilBrulebois, 2019-01-06 15:10:13
tails-persistence-shutdown-errors-2.png (150257 B) CyrilBrulebois, 2019-01-06 15:10:14
tails-persistence-shutdown-errors-3.png (214278 B) CyrilBrulebois, 2019-01-06 15:10:16

Subtasks

Related issues

Blocked by Tails - Bug #16097: Memory erasure tests regression on the devel branch Resolved 2018-11-05
Blocked by Tails - Bug #16324: Disable live-tools.service Resolved 2019-01-08

History

#1 Updated by intrigeri 2019-01-07 10:34:13

  • blocked by Bug #16097: Memory erasure tests regression on the devel branch added

#2 Updated by CyrilBrulebois 2019-01-07 10:38:19

  • Status changed from New to In Progress

Applied in changeset commit:tails|5c64ab76a36631a5c03b25c9c6933a0c7a1aa52e.

#3 Updated by intrigeri 2019-01-07 11:50:11

  • Subject changed from Enabling persistence in buster leads to issues at shutdown to Enabling persistence in Buster leads to issues at shutdown
  • Assignee changed from intrigeri to CyrilBrulebois
  • QA Check set to Info Needed

Can you reproduce this if you run the tests against an ISO with live-tools/stretch instead of live-tools/buster? I suspect we were relying on a bug that got fixed in Buster.

#4 Updated by intrigeri 2019-01-08 11:31:03

  • blocked by Bug #16324: Disable live-tools.service added

#5 Updated by intrigeri 2019-01-08 11:31:19

Hold on, I’ll do Bug #16324 first.

#6 Updated by intrigeri 2019-01-09 16:36:17

FWIW I’ve occasionally seen SquashFS I/O errors and “A stop job is running for User Manager for UID 1000” taking a while when shutting down a Tails (ISO, libvirt/QEMU) without persistence. So I suspect that at least part of the problems this ticket is about also affects systems without persistence; but I’m totally ready to believe that persistence makes it more likely (or even certain) to trigger the error conditions.

#7 Updated by intrigeri 2019-01-09 17:07:31

intrigeri wrote:
> Hold on, I’ll do Bug #16324 first.

Done! Once your resume work on the test suite for Buster, please let me know if this helps :)

#8 Updated by hefee 2019-04-05 09:22:56

  • Assignee changed from CyrilBrulebois to intrigeri
  • QA Check changed from Info Needed to Pass

Havn’t ssen this issue the last days anymore.

#9 Updated by intrigeri 2019-04-05 09:32:29

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)