Skip to contentSkip to conversation

Strange NFS happenings

DISCUSSION Ion Badulescu 2 participants 2 messages Apr 5, 2002 – Apr 8, 2002 4 messages not in the archive

Subsystems (3)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 10 lines · Mike Castle

In article <[email protected]>,

Quoted 8 lines · Trond Myklebust

The internals of shared mmap() do not allow you to overwrite a library that is already in use. Try using 'cp' to copy into libcrypto.so while ntpd is running on the server, and you will automatically get an 'ETXTBUSY' in return.
The problem is that the NFS protocol does not support leases ('cos of the statelessness requirement), and so the clients have no way of notifying the server that libcrypto should not be overwritten.

Quoted 6 lines
Quoted 3 lines

Solution: use the GNU 'install' program whenever you want to update a library. The latter creates a new file rather than overwriting the old one, and avoids this kind of mess.

Considering that ntpd WAS running on the server when I reinstalled openssl, but it did a cp -f, so it should have done an unlink then copied it in.

Except that Trond was a bit wrong about ETXTBUSY: shared libraries don't get this kind of protection, only executables do. So your cp succeeded just fine, overwrote the library, then ntpd tried to page some code in from the library and got garbage.

Never upgrade a shared library using cp, use install as Trond suggested...

Ion

Signature · 6 lines
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

_______________________________________________
NFS maillist  -  [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw

In article <[email protected]>,

Quoted 7 lines · Trond Myklebust
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

" " == Mike Castle <[email protected]> writes:

And it doesn't explain why one client saw the right file and the other two didn't.

Why do you say that? If those pages happen to be swapped out on the one client...

Linux will locally page out a library rather than dropping the page and rereading via NFS as necessary? Does it do that for executables as well?

mrc

Signature · 3 lines
     Mike Castle      [email protected]      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc