Analog artist file delte error

T

tritue

Guest
I run analog artist with IC5.1 Sub version: sub-version
5.10.41.500.2.28

Hi all,

I have few minor problems, any body has experience these?

1) If the simulation directory is remote on a linux server, I have an error
like that from time to time, then the session stop completely, I can not
start any simulation.

*Error* request.il asiiStart: error in start function, request withdrawn
("deleteFile" 1 t nil ("*Error* deleteFile: device or resource busy"
"/data/design/cgl0704/Sim/test_frontend/spectre/schematic/psf/.nfs00000000003f879c00000237"))

I have to quit the analog artist session and then start a new session before
I can simulate again. If the simulation directory is local then it work just
fine.


2)
Save state error.

From time to time I can save an analog artist session but I can not load it.
It show in the state selection box

..
...
state1

And the simulator buton will show "." or ".."

Any idea?

Thank
 
Issue (1) is an nfs lock on a file. This could be caused by a
simulation that was abruptly killed? I have seen this before when a
parametric simulation was killed.
In this case it seems like the artist session is causing the file to be
locked.
You probably need to file a SR.

(2) Make sure you dont have any mount problems for your remote servers.
That could also be the problem on (1).
Also try changing your artistStates location to a new directory, local,
to see if the problem persists.
check if a .sevSaveDir exists in the artistStates location. Also do you
do design management on the data?
If so Synchronicity (atleast) leaves a couple of files linked which ADE
does not like.

Partha
 
1) Yes, It happen when I kill the simulation (use "stop" command in analog
artist not "kill" command in linux).

2) It happen when I have an user account in the local machine. I did change
the default save directory as well but it does not help
Play with .sevSaveDir (add or remove it) I can get the state back but not
all way. If I save 10 time the same state (state1,state2, state3 ....) I can
see them in save directory but when I try to load them, I may have only 2 or
3 state appear in the load state window?
Any idea ???



<tattvamasi@gmail.com> wrote in message
news:1137627397.196904.112410@g44g2000cwa.googlegroups.com...
Issue (1) is an nfs lock on a file. This could be caused by a
simulation that was abruptly killed? I have seen this before when a
parametric simulation was killed.
In this case it seems like the artist session is causing the file to be
locked.
You probably need to file a SR.

(2) Make sure you dont have any mount problems for your remote servers.
That could also be the problem on (1).
Also try changing your artistStates location to a new directory, local,
to see if the problem persists.
check if a .sevSaveDir exists in the artistStates location. Also do you
do design management on the data?
If so Synchronicity (atleast) leaves a couple of files linked which ADE
does not like.

Partha
Click to expand...
 
tritue wrote:
I run analog artist with IC5.1 Sub version: sub-version
5.10.41.500.2.28

Hi all,

I have few minor problems, any body has experience these?

1) If the simulation directory is remote on a linux server, I have an error
like that from time to time, then the session stop completely, I can not
start any simulation.

*Error* request.il asiiStart: error in start function, request withdrawn
("deleteFile" 1 t nil ("*Error* deleteFile: device or resource busy"
"/data/design/cgl0704/Sim/test_frontend/spectre/schematic/psf/.nfs00000000003f879c00000237"))

I have to quit the analog artist session and then start a new session before
I can simulate again. If the simulation directory is local then it work just
fine.


2)
Save state error.

From time to time I can save an analog artist session but I can not load it.
It show in the state selection box

.
..
state1

And the simulator buton will show "." or ".."

Any idea?

Thank
Click to expand...

What is the OS release on your file server ? on your clients ?

I had a similar problem (issue 2) few months back when I first installed
RHEL 4.0 ES on our brand new file server and we have RHEL 3.0 WS on our
Linux clients. Problem went away after I reinstalled RHEL 3.0 ES on the
server. Issue 1 is probably also related to nfs file locking. Basically
you want to keep the same OS release on both your server and clients

Hope this helps,
Kien
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top