"Possible full disk" error message in Ansys Design Space 1

[wildsurfer123]

Hi folks,

I've been using Ansys Design Space for a few months now, I thought I had experienced all the possible error messages and so far I (with the IT guy ) managed to find solutions or at least workarounds, but this time we're stuck.

I'm trying to run a modal analysis with a structural analysis as initial condition. I've done this dozens of times, with nearly identical cad files (every time we change something we re-run an analysis) and strictly identical parameters. The analysis itself shouldn't be that difficult for my computer (300000 nodes and 100000 elements) and not that disk-space-hungry since I look for nodes only in the 0-150Hz range, and like I said it worked fine before, but this time after 2 hours of calculation I get a "possible full disk" error that of course stops the analysis. Here's the exact message :

 *** ERROR ***                           CP =    4220.062   TIME= 13:23:23
 Input/Output error on unit =20.  Possible full disk.

 *** WARNING ***                         CP =    4220.422   TIME= 13:23:26
 An error has occurred writing to the file =9 which may imply a full disk.

 The system I/O error = 28.  Please refer to your system documentation   
 on I/O errors.  

 *** FATAL ***
 Random write error on unit=9 possible full disk.
 I/O status error=28

All my data is saved on my D: partition which still has 25gb of free space, and my C: partition has 40gb left, so disk space shouldn't be a problem and the IT guy told me there are no disk space management rules for users, I can use the whole disk.
What I find weird is that error 28 on windows means that the printer is out of paper, error 28=full disk would mean I'm running linux, which I'm not.
Here are my computer's specifications :

Windows Xp Professional 32bits SP3
4Gb RAM, 3Gb switch activated, 6Gb pagefile
Intel Xeon E5420
Nvidia Quadro FX1700
Ansys Design Space v11 (the licence file says v2007.0830)

So guys if you have any idea, I would be very grateful

Maxime

 

[ansysfreak]

Hi

So you are solving on d.
It there also enough space on this partion while solving?

regards

 

[wildsurfer123]

Yes, plenty of space !

If just found the answer, thanks to a few posts at xansys.org. I was letting Ansys choose the solver, resulting in the sparse (=direct) solver being used. It turns this solver is extremely disk-space-hungry and ansys usually decides to stop the analysis before you could run out of disk space. The solution is simple : use the pcg (=iterative) solver.