Topic:
Volume in use by another process.

Description:
 

Solution:
The error message is due to the project having a problem accessing the seismic
volume file(s).  The problem could be due to:
1. Lack of disk space.
   To check for disk space:
	Session Manager > Project > Update; select project and not the
	dsl(s) associated with the project; each dsl associated with the 
	project should have a listing with the number of kbytes still 
	available on the disk; if any of the dsls have limited space you
	should clear some things off the disk and/or add additional dsl(s)
	to your project
2. Restricted permissions on disk files:
	Check the dsl(s) associated with the project as in #1 above.  On a
	unix level, 'cd' to the dsl(s) and check the permissions on all the
	files in the dsl(s).  If the permissions are restricted, open them
	with the 'chmod' command.
3. The disk where the 'vvol' (seismic vertical volumes) resides is not mounted:
	Check on the UNIX level so that the dsl(s) associated to the project
	are actually accessible (i.e. Can they be accessed on the UNIX level?)
4. Verify that the *key files for the 'vvol' file(s) are on the same disk as the
        primary vvol file which is the first vvol file created for the class:
	The 'vvol' file(s) contains a group of *key files which contain 
	information about accessing the 'vvol' file.  The *key files are as 
	follows: test_vvol_key.dat, test_vvol_key.fpb and test_vvol_key.idx,
	where 'test' is a combination of the first 5 characters the survey and
        class names of the seismic data.  Check the dsl(s) so that the three
        *key files are on the same dsl as the primary 'vvol' file.  If the *key
        files are not on the same dsl as the primary 'vvol' file, it is likely
        that they are on one of the other dsls associated with the project.  If
        so, move the *key files to the same dsl as the primary 'vvol' file.
5. Verify that the *key files are not 0 byte size:
	Check on the UNIX level, as in #4 above for the location of the *key
	files and make certain they are not 0 byte size files.  If so, then an
        index file rebuild, or a restore from backup, or a reload of the data
        may be necessary. Also, check for too large > 2Gb.




Last Modified on: 01-JUN-99