EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Vxworks nfs write error?
From: Ron Sluiter <[email protected]>
To: "Lawson, Gregory S." <[email protected]>, "[email protected]" <[email protected]>
Date: Mon, 27 Mar 2017 13:29:48 -0500
If you are not already using the save_restoreSet_NFSHost() command, I highly recommend it.

We here at the APS had a lot of autosave problems with VxWorks based IOCs having stale file handles.
This was resolved when Tim Mooney added the save_restoreSet_NFSHost() command to the autosave module.

4. Set NFS host (optional, only available on vxWorks and RTEMS)

Specify the NFS host from which save files will be read at restore time, and to which they will be written at save time, by calling the function
	save_restoreSet_NFSHost("oxygen", "164.54.49.4")

When autosave manages its own NFS mount, as this command directs it to do, it can fix a stale file handle by dismounting and remounting the file system.


Ron

On 3/27/2017 8:47 AM, Lawson, Gregory S. wrote:
As it turns out, this error was caused by a broken NFS mount at the IOC.
The problem has been solved.  There were some questions about OS version,
and NFS version..

RedHat Enterprise Linux 6.6 (32 bit)
NFS package version 3.2.29  (the ioc connects using nfs V3)

Thanks for the help!

Greg

On 3/24/17, 10:27 PM, "Paduan Donadio, Marcio" <[email protected]>
wrote:

Hello, Greg.

Here in SLAC, we faced the same problem but under Linux. We first ran the
IOC with user1, generating autosave files with user1 as owner and next,
we ran it with user2. The result was that on the second time, autosave
tried to fchmod a file as user2, having user1 as the owner of the file,
what is not allowed in Linux, and probably in your NFS server.

If you change the owner of your autosave files, probably you will not see
the messages anymore.

Even having this solution, I see 2 improvement opportunities here:
1 - autosave is changing file permissions by default and does this
silently. I think this should be an option to be chosen by the IOC
engineer.
2 - autosave shows error -1 and this can be anything. There is no way to
diagnose what is going on.

I am working on a patch with some suggestions to address this, and I will
make a GitHub pull request soon.

I don't have experience with VxWorks, but maybe it can work for you,
Greg. For now, if you want to build autosave without the need of changing
file permissions, you can:

- modify asApp/src/Makefile, adding:
USR_CPPFLAGS += -DSET_FILE_PERMISSIONS=0

- modify asApp/src/save_restore.c, changing:
#ifndef _WIN32
 #ifndef SET_FILE_PERMISSIONS
   #define SET_FILE_PERMISSIONS 1
 #endif
#endif

Best regards,

Márcio.

________________________________________
De: [email protected] <[email protected]> em nome
de J. Lewis Muir <[email protected]>
Enviado: quarta-feira, 22 de março de 2017 11:13
Para: Lawson, Gregory S.
Cc: [email protected]
Assunto: Re: Vxworks nfs write error?

On 03/17, Lawson, Gregory S. wrote:
Host is RHELWS kernel 2.6.32-642.
What version of RHEL is that?

What version of NFS is the server providing?

Regards,

Lewis




References:
Vxworks nfs write error? Lawson, Gregory S.
Re: Vxworks nfs write error? J. Lewis Muir
Re: Vxworks nfs write error? Paduan Donadio, Marcio
Re: Vxworks nfs write error? Lawson, Gregory S.

Navigate by Date:
Prev: CSS-BOY change field satus in runtime Miguel
Next: Two VxWorks IOCs in one VME Crate keith.baker
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Vxworks nfs write error? Lawson, Gregory S.
Next: Multi-monitor for CSS opi palak shimpee
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·