On 26.10.11 23:44, Russell Coker wrote:
umount/mount on client?
No, umounting on the client didn't work and couldn't work unless the server kept track of which clients had previously used the files in question.
True. Now if I could just rattle decades-old memory to recall what I did on the server. It certainly didn't involve editing configs. Ah, shoulda rummaged in extra-cranial memory before the last post. In those _Solaris days_, I made a note: » nfsd may remain oblivious to changes, until: /etc/init.d/nfs-kernel-server restart # Or sufficient?: /etc/init.d/nfs-kernel-server reload # which simply does: /usr/sbin/exportfs -r # Sync /var/lib/nfs/xtab # with /etc/exports. « Sleep beckons, so I won't install NFS, and try it on linux just now, but it ought to be reasonably similar, I expect.
It should be possible for the server to do such tracking when the server has enough uptime for client caches to have expired (which would surely happen in less than 2 weeks). But I guess that they don't do such things.
True too. In a half-ideal *nix world, the period ought to be settable in the config. Anyway, the space should have been free immediately, my brain tells me (at 1 a.m. admittedly). The server was in need of a whack before the file deletion, I think. Erik -- Give a man a computer program and you give him a headache, but teach him to program computers and you give him the power to create headaches for others for the rest of his life. - R. B. Forest