ureadahead trying to read entire filesystem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
ureadahead (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
MAAS Version 2.1.1+bzr5544-
As shown in bug 1635560 and specifically in https:/
These are the log messages immediately before the spamminess:
Nov 22 08:32:32 faraday systemd[1]: Starting Stop ureadahead data collection...
Nov 22 08:32:32 faraday systemd[1]: Stopping Read required files in advance...
Nov 22 08:32:32 faraday systemd[1]: Started Stop ureadahead data collection.
The ureadahead lines are responsible for the vast majority of the installation log
⟫ cat faraday-
78777
⟫ grep ureadahead faraday-
76799
MAAS doesn't really do anything with ureadahead nor curtin does. However, by looking at the logs I've found this:
Nov 22 08:31:25 faraday systemd[1]: Started Stop ureadahead data collection 45s after completed startup. events/ fs/open_ exec/enable: Ignored relative path
[...]
Nov 22 08:31:45 faraday cloud-init[1125]: Processing triggers for ureadahead (0.100.0-19) ...
[...]
Nov 22 08:31:47 faraday cloud-init[1125]: Processing triggers for ureadahead (0.100.0-19) ...
[...]
Nov 22 08:32:32 faraday systemd[1]: Starting Stop ureadahead data collection...
Nov 22 08:32:32 faraday systemd[1]: Stopping Read required files in advance...
Nov 22 08:32:32 faraday systemd[1]: Started Stop ureadahead data collection.
Nov 22 08:32:32 faraday ureadahead[474]: ureadahead:
So I wonder if cloud-init has changed something here that causes ureadahead from starting the indexing of files, or whether this is something that has changed in the cloud image itself (from CPC) or in Ubuntu itself.