ureadahead, set by ubuntu-standard, is not needed with systemd

Bug #1446283 reported by dino99
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Invalid
High
Unassigned
upstart
Invalid
Undecided
Unassigned
ubuntu-meta (Ubuntu)
Invalid
High
Unassigned

Bug Description

Description:

- ubuntu vivid has set systemd as default and upstart the alternative choice
- systemd comes with its own readahead implementation
- ubuntu-standard install ureadahead (depends on)

Now ubuntu-standard needs to deal with the two choices:
- need to install ureadahead if upstart is used
- if systemd is used, then ureadahead should be ignored

The always ureadahead installation push lot of unexpected flood into journalctl
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1429098 (comments #17 +)

*********************************************************
Possible solution:
- adding ureadahead as a dependency of upstart-sysv
- removing ureadahead as a dependency of ubuntu-standard
*********************************************************

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubuntu-minimal 1.334
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Mon Apr 20 17:31:07 2015
JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found.
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
dino99 (9d9) wrote :
dino99 (9d9)
tags: added: wily
description: updated
Revision history for this message
dino99 (9d9) wrote :

Feedback:

that ureadahead flood in journalctl on Wily is not seen with the latest kernel 4.1.0.3.3 (wily-proposed), as it was seen previously.

Revision history for this message
dino99 (9d9) wrote :

Please ignore the comment #4 above: on the next boot due to some crashes (upstart, xorg, gnome-shell) the ureadahead comments are again flooding journalctl

dino99 (9d9)
description: updated
summary: - [systemd] [ureadahead] Confusing features running twice
+ [systemd] unexpected ureadahead executed by ubuntu-meta
dino99 (9d9)
summary: - [systemd] unexpected ureadahead executed by ubuntu-meta
+ ureadahead, set by ubuntu-minimal, is not needed with systemd
description: updated
no longer affects: systemd
dino99 (9d9)
tags: added: xenial
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: ureadahead, set by ubuntu-minimal, is not needed with systemd

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-meta (Ubuntu):
status: New → Confirmed
Changed in ubuntu-meta (Ubuntu):
importance: Undecided → High
Changed in hundredpapercuts:
status: New → Confirmed
importance: Undecided → High
Changed in upstart:
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

ubuntu-standard still 'recommends' ureadahead in yakkety.

summary: - ureadahead, set by ubuntu-minimal, is not needed with systemd
+ ureadahead, set by ubuntu-standard, is not needed with systemd
description: updated
Changed in ubuntu-meta (Ubuntu):
status: Confirmed → Fix Released
Steve Langasek (vorlon)
Changed in ubuntu-meta (Ubuntu):
status: Fix Released → Triaged
dino99 (9d9)
tags: added: yakkety
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

This is longer true with 217 and higher, as systemd implementation has been removed.
        * systemd's readahead implementation has been removed. In many
          circumstances it didn't give expected benefits even for
          rotational disk drives and was becoming less relevant in the
          age of SSDs. As none of the developers has been using
          rotating media anymore, and nobody stepped up to actively
          maintain this component of systemd it has now been removed.

Closing this bug.

Changed in ubuntu-meta (Ubuntu):
status: Triaged → Invalid
Changed in upstart:
status: Confirmed → Invalid
Changed in hundredpapercuts:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.