udevadm: systemd-udev-settle.service is deprecated. Please fix zfs-loa

1. udevadm: systemd-udev-settle.service is deprecated. Please fix zfs-load-module.service, zfs-import-cache.service not to pull it in.
2. ░░ Subject: systemd-udev-settle.service is deprecated.
3. ░░ Defined-By: systemd
4. ░░ Support: http://www.ubuntu.com/support
5. ░░
6. ░░ Usage of the systemd service unit systemd-udev-settle.service is deprecated. It
7. ░░ inserts artificial delays into the boot process without providing the
8. ░░ guarantees other subsystems traditionally assumed it provides. Relying on this
9. ░░ service is racy, and it is generally a bug to make use of it and depend on it.
10. ░░
11. ░░ Traditionally, this service's job was to wait until all devices a system
12. ░░ possesses have been fully probed and initialized, delaying boot until this
13. ░░ phase is completed. However, today's systems and hardware generally don't work
14. ░░ this way anymore, hardware today may show up any time and take any time to be
15. ░░ probed and initialized. Thus, in the general case, it's no longer possible to
16. ░░ correctly delay boot until "all devices" have been processed, as it is not
17. ░░ clear what "all devices" means and when they have been found. This is in
18. ░░ particular the case if USB hardware or network-attached hardware is used.
19. ░░
20. ░░ Modern software that requires some specific hardware (such as a network device
21. ░░ or block device) to operate should only wait for the specific devices it needs
22. ░░ to show up, and otherwise operate asynchronously initializing devices as they
23. ░░ appear during boot and during runtime without delaying the boot process.
24. ░░
25. ░░ It is a defect of the software in question if it doesn't work this way, and
26. ░░ still pulls systemd-udev-settle.service into the boot process.
27. ░░
28. ░░ Please file a bug report against the following units, with a request for it to
29. ░░ be updated to operate in a hotplug fashion without depending on
30. ░░ systemd-udev-settle.service:
31. ░░
32. ░░     zfs-load-module.service, zfs-import-cache.service

复制代码

这是一个还没汉化的日志提示信息，那么翻译一下

1. udevadm[534]：systemd-udev-settle.service 已被弃用。请修复 zfs-load-module.service 和 zfs-import-cache.service，使它们不再依赖它。
2. ░░ 主题：systemd-udev-settle.service 已被弃用。
3. ░░ 定义者：systemd
4. ░░ 支持：http://www.ubuntu.com/support
5. ░░ 使用 systemd 服务单元 systemd-udev-settle.service 已被弃用。
6. ░░ 它会向启动过程中插入人为的延迟，而没有提供其他子系统传统上认为它所提供的保证。
7. ░░ 依赖这个服务是有风险的，并且通常使用它并依赖于它是一种错误。
8. ░░
9. ░░ 传统上，这个服务的工作是等待系统拥有的所有设备都完全探测和初始化完毕，延迟启动直到这个阶段完成。
10. ░░ 然而，现在的系统和硬件通常不再以这种方式工作，硬件现在可能随时出现，并可能需要任何时间来探测和初始化。
11. ░░ 因此，在一般情况下，不再可能正确地延迟启动直到“所有设备”都被处理，因为不清楚“所有设备”意味着什么以及何时它们会被找到。
12. ░░ 特别是在使用 USB 硬件或网络连接硬件的情况下。
13. ░░
14. ░░ 现代软件如果需要某些特定硬件（如网络设备或块设备）来运行，应该只等待它需要的特定设备出现。
15. ░░ 否则应该异步操作，在启动和运行时初始化出现的设备，而不延迟启动过程。
16. ░░
17. ░░ 如果软件不是这种方式工作，并且仍然在启动过程中引入 systemd-udev-settle.service，则是该软件的问题。
18. ░░
19. ░░ 请针对以下单元提交一个错误报告，并要求更新它们以在没有依赖 systemd-udev-settle.service 的情况下以热插拔方式操作：
20. ░░
21. ░░     zfs-load-module.service, zfs-import-cache.service

复制代码

systemd-udev-settle.service 被弃用意味着，在未来的版本中它可能会以其它方式存在。为了向后兼容，不应该对它进行修改，应该让两个 zfs 模块不要依赖它。

• 利用 zfs 的用户：根据情况用 systemctl list-units --type=mount 查出要挂载的设备，将两个 zfs 模块的 After / Requires =.mount
  
• 其它用户
  

1. sudo systemctl mask zfs-load-module.service zfs-import-cache.service
2. # 执行成功会显示
3. Created symlink /etc/systemd/system/zfs-load-module.service → /dev/null.
4. Created symlink /etc/systemd/system/zfs-import-cache.service → /dev/null.

复制代码

免责声明：如果侵犯了您的权益，请联系站长，我们会及时删除侵权内容，谢谢合作！更多信息从访问主页：qidao123.com:ToB企服之家，中国第一个企服评测及商务社交产业平台。