On 03/09/2016 01:11 PM, Greg Freemyer wrote:
# NFS MOUNT HERE 10.200.3.230:/mnt/pacers1/kvm672/kvm672 /srv_new nfs rw,relatime,vers=3 0 0
# NFS dependent mounts here /srv_new/sftp-container-large /srv/sftp ext4 nofail,loop 0 0 /srv_new/portal_backup_container /home/portal_backup/portal_backup ext4 nofail,loop 0 0
Oh, I see what you're doing! I woud;'t do it that way. back in the 1980s working with SUN workstations and *EVERYTING* being NFS it was done with symlinks. When I did similar on opensuse with my laptop connected to the home LAN I worked it out this way: I had a /mnt/nfs/ main directory had under that things like /mnt/nfs/homelan/downloads So there was a homelan:/home.anton/dowloads /mnt/nts/homelan/downloads nfs \ rw,rsize..,wsize...,_netdev 0 2 There was also awaylan:/yamma/yamma/dowloads /mnt/nts/homelan/downloads nfs \ rw,rsize..,wsize...,_netdev 0 2 I then had symlink from /home/anton/downloads to /mnt/nts/homelan/downloads If I was working in a coffee shop and didn't have a connection to neither homelan nor awaylan then my downloads directory appeared empty. The "_netdev" is important. The symlink avoid the bind mount that seems to be giving you problems.
===
The NFS server doesn't allow me to control of the file metadata (ownership etc.). In particular it forces all files on it to be owned by one UID / GID.
So as root I've created a couple large container files which I mount via loopback. Within the containers I have full control of the filesystem metadata (file ownership, etc).
I take it to mean that you can't run rpc.imapd ? You do realise that imapd allows *arbitrary* remapping of uid and gid? So if the remote files are 'owned' rw-r----- by hpotter;gryffindor you can map them to, for example, gregf:users -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org