Andrew Bird
Andrew Bird
Oh yes, and I tried `nolock` on a test mount and although the mount command took the option, nothing extra appeared in mount entry. ~~~ oliver:/export/clients on /a type nfs4...
Nfsv4 is new to me, but Internet seems to suggest that lock/nolock/local_lock=* are v2/v3 options and ignored on v4.
Yes, but then no xattrs, I suppose ~~~ # mount -o vers=3,local_lock=all oliver:/export/clients /a Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /lib/systemd/system/rpc-statd.service. # grep oliver:/export/clients /proc/$$/mounts oliver:/export/clients /a nfs rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,hard, proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.3.45,mountvers=3,mountport=34668, mountproto=udp,local_lock=all,addr=192.168.3.45 0...
I guess we should ask @nnn19 whether the files on the server are being accessed from multiple nfs client machines?
Sorry, I forgot to say you need to do `make -C test/fpu clean all` in the build directory first.
Seem okay to me. Remember though that it creates image files with a hole, not padded with zeros.
Actually I just did `mkfatimage16 -k 1024 test1.img` and although its size in DOS shows 1M size, its size on disk seems to be have been truncated rather than made...
It seems you need to specify `-p` also to create the full size (as sparse) file. I'm not quite sure what the reasoning is for the default.
I think the answer is -p, but the default makes no sense.
I don't know who offhand, but it's possible it was me I'd have to check. I do like sparse files.