ub22@gmx.net wrote:
# ls -l / | grep home lrwxrwxrwx 1 root root 11 Jun 4 21:50 home -> /home.server/ drwxr-xr-x 1 root root 52 Apr 4 10:39 home.local drwxr-xr-x 10 root root 4096 Aug 1 12:36 home.server # mount | grep home /dev/nvme0n1p2 on /home.local type btrfs (rw,relatime,ssd,space_cache,subvolid=263,subvol=/@/home) server:/home on /home.server type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=x.y.z.2,local_lock=none,addr=x.y.z.1) server:/home/users on /home.server/users type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=x.y.z.2,local_lock=none,addr=x.y.z.1) # cat /etc/fstab | grep home UUID=123 /home.local btrfs subvol=/@/home 0 0 server:/home /home.server nfs defaults 0 0
Seams to be an issue with the linked /home (which I use to be able to use the device in my network with mounted /home from Server and stand alone). If you need a symlink home -> /home.server/ I would suggest to use a bind mount instead of a symlink. Two reasons:
* Many programs use files in $HOME and many of them could not deal consistently with symlinks. For instance they write pathes like /home.server/user/some-file1 and /home/user/some-file2 in config files. * Bind mounts will not result in errors like you described. Offline updates (from CDROM, ISO) may still be an issue. I haven't tested, if the Installer uses the bind mounts from /etc/fstab. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org