All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sev Binello <sev@bnl.gov>
To: nfs@lists.sourceforge.net
Subject: executables crash when moved
Date: Wed, 15 Feb 2006 12:58:46 -0500	[thread overview]
Message-ID: <43F36BD6.7010408@bnl.gov> (raw)

We have had a consistent problem of executables shared over NFS crashing
when new executables are released.

    Before a new executable replaces an older one with a cp,
    we mv the executable to a fallback dir and rename it.
    We have 2 renaming schemes,
    either .old, .older, .oldest or  append a date to the old executable.
   
    This used to work fine when the nfs sever was solaris,
    however since we migrated it to redhat linux WS,
    we find that the executables crash with a SIGBUS.
   
    The executables don't necessarily crash right away,
    as a matter of fact we can't intentionally reproduce the crash.
    Which leads me to believe it is cache related.

    Has anyone experienced a similar problem,
     and come up with a solution ?

Thanks
-Sev

-- 

Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
sev@bnl.gov



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2006-02-15 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 17:58 Sev Binello [this message]
2006-02-15 19:31 ` executables crash when moved Trond Myklebust
2006-02-15 21:29   ` Sev Binello

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43F36BD6.7010408@bnl.gov \
    --to=sev@bnl.gov \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.