We've been experiencing the following problem on HP 700 AFS clients
running AFS 3.3a and HP-UX 9.03...
After releasing a volume that contains commonly used tools (executables)
many clients will experience applications terminating with the following
error:
Pid XXXX killed due to text modification or page I/O error.
The 'file' command reports that these executables are "PA-RISC1.1 shared
executables".
If more than one instance of the process (application) is running, the
program cannot be re-run until all running instances are killed. Any
attempt to re-run the application before this time will result in the
same error being generated immediately. Note that there has been no
change in the actual executables - they are the same files.
The problem has occurred after releasing a volume and (on other occasions)
after removing replication sites for volumes. Needless to say, the fact
that applications are dying is very frustrating for our users.
How does releasing a volume or removing a replication site affect the
vnode modification time? The vnode modification time is the mechanism
that HP-UX uses to determine that an "on-disk" copy has changed relative
to a running process.
Has anyone else experienced this problem? Can someone list the situations
(vos operations?) that can lead to this occuring? Is the only solution to
*only* release volumes before all clients reboot?
Any help would be greatly appreciated.
Thanks,
Brad Black [EMAIL PROTECTED]
Bell-Northern Research Ltd. (613) 763-9811
| | | | | | | | | | | ||||
