2018-02-06, 12:42
Build #205.
With this build, all my system.d mount services fail with messages like this in the journal:
The shares are on disks which Windows mounts as mountpoints under C:\Buckets\<drive> rather than as individual Windows drive letters.
This is presumably where the 'symbolic link' happens.
This is presumably down to kernel changes in the last couple of builds, as it was OK with #203.
I am reverting to #203 until this is cleared up.
With this build, all my system.d mount services fail with messages like this in the journal:
Quote:Feb 06 10:09:31 pi3a-LEv18 systemd[1]: Reached target Network is Online.The shares in question are all on a Windows 2008 R2 server.
Feb 06 10:09:31 pi3a-LEv18 systemd[1]: media-Squeezebox.mount: Mount path /media
/Squeezebox is not canonical (contains a symlink).
Feb 06 10:09:31 pi3a-LEv18 systemd[1]: media-Squeezebox.mount: Failed to run 'mo
unt' task: Too many levels of symbolic links
Feb 06 10:09:31 pi3a-LEv18 systemd[1]: media-Squeezebox.mount: Failed with resul
t 'resources'.
Feb 06 10:09:31 pi3a-LEv18 systemd[1]: Failed to mount mount Squeezebox.
The shares are on disks which Windows mounts as mountpoints under C:\Buckets\<drive> rather than as individual Windows drive letters.
This is presumably where the 'symbolic link' happens.
This is presumably down to kernel changes in the last couple of builds, as it was OK with #203.
I am reverting to #203 until this is cleared up.