Openzfs mountpoint not empty3/17/2023 ![]() ![]() ZFS didn't mount the pool quickly enough, proxmox would create the ProxmoxĪutomatically creates certain sub-directories in certain places, and if > is starting up after zfs mounts /var, but before it can mountīack when I was using proxmox, I hit this all the time. > The only way I can see that happening is that a process (say, rsyslog) > /var/spool, /var/tmp, /var/log, /var/cache all refuse to mount, > chance to fnish mountin an associated filesystem. > or if it's a case of systemd starting processes before zfs has a > I'm not sure if it's because there is an issue with the mounting code, ![]() > whatever reason, zfs mount -a does not mount the filesystems in the > I only use ZFS - everything on my system is a zfs mount, however, for I have dozens of mount points which have this error I vaguely remember a similar situation on a Debian system with systemd but in that case, it was sufficient to enable and restart rvice. I have found a similar bug, which was about a systemd service not being enabled, but zfs-import.target is enabled, so I don't think that's it. Obviously, such a script shouldn't be necessary but it's a workaround for the moment and maybe it helps someone out there. After that, it tries to fix the bind mounts (if specified). I wrote a script that does all that and can be run on startup: It tries to mount the zpool (if not mounted already) and if that fails, it removes all empty subdirectories within the base mountpoint of the pool (e.g., /z-main specified at the top of the script) and tries to mount it again. As it's a common scheme to use bind mounts in order to export the ZFS volumes via NFS, those have to be fixed as well. Mounting it manually without removing those empty directories first fails. Whenever the system is rebooted, the pool isn't available. I feel like that shouldn't happen (if those mountpoints are created automatically, they should be removed automatically as well). It seems like those mountpoints are preventing the pool itself from being mounted. Indeed, that directory (which was created automatically) is not empty because it contains empty subdirectories, one for each ZFS volume in that pool. Trying to mount it manually fails:Ĭannot mount '/z-main': directory is not empty
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |