That is a very good observation about not having to be on startup!! After I disabled both vmware.service and virtualbox.service, I cleaned-up: delete the '/root' and then make sure to mount it from the zfs dataset.
Then I shutdown the system yesterday evening (2020-06-25). When I started the system this morning (2020-06-26): I saw that again the zfs dataset could not be mounted because a '/root' already exists, this time with an empty ".cache" folder in it. So it seems you were right about the vwmware or virtualbox that they use pulseaudio as root. But that is not the real issue: problem is with the ".cache" folder which is created at shutdown 'after' the zfs dataset is unmounted, just like you said. I'm not sure how to investigate what happens at shutdown, but I'll try to find out. Meanwhile it's clear this not a pulseaudio issue ==> this ticket should be closed (I'm not sure if I can do that, or you or someone else needs to do it). Daniel, thank you very much for your quick and very helpful responses: I appreciate it a lot! Filesystem details after a night of shutdown: ----------------- root@minighost:~# pwd /root root@minighost:~# ls -la total 10 drwxr-xr-x 3 root root 3 Jun 26 07:12 . drwxr-xr-x 34 root root 38 Jun 25 20:12 .. drwx------ 2 root root 2 Jun 25 20:23 .cache root@minighost:~# tree -a . └── .cache 1 directory, 0 files root@minighost:~# ----------------- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884455 Title: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use 'zfs' and have /root as its own dataset which is mounted during startup by 'zfs-mount.service'. At one of the latest upgrades, the 'zfsutils-linux' package failed to update because the service 'zfs-mount' service had an issue and could not mount the '/root' dataset because the '/root' directory was not empty (temporary solution was to rename /root and call 'zfs mount' again). Further investigation shows that everytime at startup, the /root directory is created before the 'zfs-mount.service' has a chance to mount the 'root' dataset. The culprit seems to be something pulseaudio related: the content of /root folder after startup is as follows: ----------------- root@minighost:~# tree -a /root . ├── .cache └── .config └── pulse └── fe1417537ae0451abdb60c5df28fe825-runtime -> /tmp/pulse-PKdhtXMmr18n 4 directories, 0 files root@minighost:~# ----------------- Extra details: - Ubuntu release: ----------------- root@minighost:~# lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ----------------- - status of 'zfs-mount.service' is the following: ----------------- root@minighost:~# systemctl status zfs-mount ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-06-21 12:56:08 CEST; 6h ago Docs: man:zfs(8) Process: 2062 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2062 (code=exited, status=1/FAILURE) Jun 21 12:56:08 minighost systemd[1]: Starting Mount ZFS filesystems... Jun 21 12:56:08 minighost zfs[2062]: cannot mount '/root': directory is not empty Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Jun 21 12:56:08 minighost systemd[1]: Failed to start Mount ZFS filesystems. root@minighost:~# ----------------- - software versions: ----------------- root@minighost:~# apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@minighost:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.1 Candidate: 0.8.3-1ubuntu12.1 Version table: *** 0.8.3-1ubuntu12.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ----------------- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: dumi 2419 F.... pulseaudio CasperMD5CheckResult: skip Date: Sun Jun 21 19:17:20 2020 InstallationDate: Installed on 2018-09-08 (651 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-24 (57 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
