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  2017  <20182019  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  2017  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Re: Problem with synApps autosave
From: 龙巍 via Tech-talk <[email protected]>
To: "mooney, tim m." <[email protected]>
Cc: [email protected]
Date: Wed, 26 Dec 2018 09:50:27 +0800 (GMT+08:00)

Thank you. You're absolutely right. Our autosave didn't use nfsDrv to read and write files, but used netDrv instead.

We examined NFS configuration again carefully and found that the Shared folder path for NFS was not exactly the same as the path name set in the st.cmd file. This was a very low-level mistake. We fixed it and the error message disappeared.


-----原始邮件-----
发件人:"Mooney, Tim M." <[email protected]>
发送时间:2018-12-26 01:51:08 (星期三)
收件人: "龙巍" <[email protected]>
抄送:
主题: Re: Problem with synApps autosave

I don't know the answer, but I have a clue.  When nfsMount() fails, vxWorks uses netDrv instead of nfsDrv.  netDrv does some things right, so autosave is able to read and write files, but it can't change file permissions, check the file's date, or use ioctl() to find out if the file has been flushed all the way to disk.  The "S_netDrv_UNKNOWN_REQUEST" message shows that you're in this situation.


It may be that the vxWorks user doesn't have permission to mount file systems.  I don't do the network administration that allows our vxWorks systems to use NFS, so I can't guess why.


We use vxWorks 6.9.4.1, but I think the reason is that, in earlier versions of vxWorks, the "ls" command doesn't work, so other uses of autosave (notably, configMenu) don't work.  It also may be that the version of NFS that the file server uses doesn't match the version vxWorks is using.  (Again, I'm not a net admin, so I don't know the details.)


Tim Mooney ([email protected]) (630)252-5417
Beamline Controls Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab


From: [email protected] <[email protected]> on behalf of 龙巍 via Tech-talk <[email protected]>
Sent: Tuesday, December 25, 2018 4:16:54 AM
To: [email protected]
Subject: Problem with synApps autosave
 
Hi,

  When we tried to use the synApps-autosave in a PowerPC VxWorks IOC (base 3.15.4 / autosaveR 5-7-1), There were a lot of error?/Annoying messages appear periodically. But the autosave was able to work properly.
  The NFS configuration is :" /home/long/ntfDir *(insecure,rw,sync,no_root_squash)".
  We also checked the IOC and the nfs server time, there were no problems.

Here is the report:

boot device          : motetsec
unit number          : 0
processor number     : 0
host name            : RCSRFDevelopment
file name            : /home/long/Epics/bootdir/vxWorks
inet on ethernet (e) : 192.168.0.67:ffffff00
host inet (h)        : 192.168.0.88
user (u)             : long
flags (f)            : 0x0
target name (tn)     : cpci6200
startup script (s)   : /home/long/nfsDir/asExample/iocBoot/iocasExample/st.cmd

Loading... 2152208 + 404336
Starting at 0x100000...


Adding 7645 symbols for standalone.
 

 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
      ]]]]]]]]]]]  ]]]]     ]]]]]]]]]]       ]]              ]]]]         (R)
 ]     ]]]]]]]]]  ]]]]]]     ]]]]]]]]       ]]               ]]]]           
 ]]     ]]]]]]]  ]]]]]]]]     ]]]]]] ]     ]]                ]]]]           
 ]]]     ]]]]] ]    ]]]  ]     ]]]] ]]]   ]]]]]]]]]  ]]]] ]] ]]]]  ]]   ]]]]]
 ]]]]     ]]]  ]]    ]  ]]]     ]] ]]]]] ]]]]]]   ]] ]]]]]]] ]]]] ]]   ]]]] 
 ]]]]]     ]  ]]]]     ]]]]]      ]]]]]]]] ]]]]   ]] ]]]]    ]]]]]]]    ]]]]
 ]]]]]]      ]]]]]     ]]]]]]    ]  ]]]]]  ]]]]   ]] ]]]]    ]]]]]]]]    ]]]]
 ]]]]]]]    ]]]]]  ]    ]]]]]]  ]    ]]]   ]]]]   ]] ]]]]    ]]]] ]]]]    ]]]]
 ]]]]]]]]  ]]]]]  ]]]    ]]]]]]]      ]     ]]]]]]]  ]]]]    ]]]]  ]]]] ]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]       Development System
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]]
 ]]]]]]]]]]]]]]]]]]]]]]]]]]]       VxWorks 6.8
 ]]]]]]]]]]]]]]]]]]]]]]]]]]       KERNEL: WIND version 2.13
 ]]]]]]]]]]]]]]]]]]]]]]]]]       Copyright Wind River Systems, Inc., 1984-2009

 CPU: Emerson CPCI6200-13-2G       - MPC8572 (UP).  Processor #0.
 Memory Size: 0x7fdff000.  BSP version 2.0/0.
 Created: Dec 25 2018, 16:10:11
 ED&R Policy Mode: Deployed
 WDB Comm Type: WDB_COMM_END
 WDB: Ready.
Executing startup script '/home/long/nfsDir/asExample/iocBoot/iocasExample/st.cmd'...

## Example vxWorks startup file

## The following is needed if your board support package doesn't at boot time
## automatically cd to the directory containing its startup script
cd "/home/long/nfsDir/asExample"
value = 0 = 0x0


## You may have to change asExample to something else
## everywhere it appears in this file
ld <bin/vxWorks-mpc8572/asExample.munch
value = 154994480 = 0x93d0730 = '0'

epicsEnvSet("EPICS_TS_MIN_WEST", -420)
value = 0 = 0x0
epicsEnvSet("EPICS_TS_NTP_INET","192.168.0.68")
value = 0 = 0x0

dbLoadDatabase "dbd/asExample.dbd"
value = 0 = 0x0
asExample_registerRecordDeviceDriver pdbbase
value = 0 = 0x0

save_restoreSet_Debug(0)
value = 0 = 0x0
save_restoreSet_IncompleteSetsOk(1)
value = 1 = 0x1
save_restoreSet_DatedBackupFiles(1)
value = 1 = 0x1
set_savefile_path("/home/long/nfsDir","");
value = 0 = 0x0
set_requestfile_path("/home/long/nfsDir","")
value = 0 = 0x0
set_pass0_restoreFile("auto_settings.sav")
value = 0 = 0x0
set_pass1_restoreFile("auto_settings.sav")
value = 0 = 0x0

save_restoreSet_NumSeqFiles(5)
value = 5 = 0x5
save_restoreSet_SeqPeriodInSeconds(600)
value = 600 = 0x258 = 'X'
save_restoreSet_RetrySeconds(60)
value = 60 = 0x3c = '<'
save_restoreSet_CAReconnect(1)
value = 1 = 0x1
save_restoreSet_CallbackTimeout(-1)
value = -1 = 0xffffffff
save_restoreSet_NFSHost("RCSRFDevelopment","192.168.0.88")
save_restore: Can't mount '/home/long/nfsDir'
value = 46 = 0x2e = '.'

## Load record instances
dbLoadTemplate "db/user.substitutions"
value = 0 = 0x0
dbLoadRecords "db/dbSubExample.db", "user=long"
value = 0 = 0x0

## Set this to see messages from mySub
#mySubDebug = 1

## Run this to trace the stages of iocInit
#traceIocInit


iocInit
Starting iocInit
############################################################################
## EPICS R3.15.4 $Date: Fri 2016-05-27 08:54:04 +0200$
## EPICS Base built Dec 25 2018
############################################################################
reboot_restore: entry for file 'auto_settings.sav'
reboot_restore: Found filename 'auto_settings.sav' in restoreFileList.
*** restoring from '/home/long/nfsDir/auto_settings.sav' at initHookState 6 (before record/device init) ***
reboot_restore: done with file 'auto_settings.sav'

reboot_restore: entry for file 'auto_settings.sav'
reboot_restore: Found filename 'auto_settings.sav' in restoreFileList.
*** restoring from '/home/long/nfsDir/auto_settings.sav' at initHookState 7 (after record/device init) ***
reboot_restore: done with file 'auto_settings.sav'

iocRun: All initialization complete
value = 0 = 0x0

create_monitor_set("auto_settings.req",5,"")
save_restore: Can't mount '/home/long/nfsDir'
value = 0 = 0x0

## Start any sequence programs
#seq &sncExample, "user=long"

Done executing startup script '/home/long/nfsDir/asExample/iocBoot/iocasExample/st.cmd'.

-> auto_settings.sav: 1 of 1 PV's connected
write_it: fchmod returned -1
save_restore:write_it: ioctl(,FIOSYNC,) returned -1 [181225-161129]
../save_restore.c(1773): [0x290004]=write_it:S_netDrv_UNKNOWN_REQUEST
save_restore:write_it: file time is different from IOC time [181225-161129], difference=1545729089.000000s
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
save_restore:write_save_file: Can't write save file. [181225-161129]
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***


-> date

2018/12/25 16:11:57.974480
value = 27 = 0x1b
-> save_restore: attempting to remount filesystem
save_restore: failed to remount '/home/long/nfsDir'
write_it: fchmod returned -1
save_restore:write_it: ioctl(,FIOSYNC,) returned -1 [181225-161229]
../save_restore.c(1773): [0x290004]=write_it:S_netDrv_UNKNOWN_REQUEST
save_restore:write_it: file time is different from IOC time [181225-161229], difference=1545729149.000000s
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
save_restore:write_save_file: Can't write save file. [181225-161229]
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

  With the message above, what do you think the problem is? And, How to fix it?
 
 
Thanks,
Wei Long


References:
Problem with synApps autosave 龙巍 via Tech-talk

Navigate by Date:
Prev: Problem with synApps autosave 龙巍 via Tech-talk
Next: asynError in write on Power PMAC IOC Chanaka via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Problem with synApps autosave 龙巍 via Tech-talk
Next: asynError in write on Power PMAC IOC Chanaka via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
ANJ, 31 Dec 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·