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.
[...]
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:events/fs/open_exec/enable:
Ignored relative path
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.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643838
Title:
ureadahead trying to read entire filesystem
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1643838/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
