Note: This discussion is about an older version of the COMSOL Multiphysics® software. The information provided may be out of date.

Discussion Closed This discussion was created more than 6 months ago and has been closed. To start a new discussion with a link back to this one, click here.

Input/Output Error Eigenvalue Solver

Please login with a confirmed email address before reporting spam

While trying to complete a parametric sweep eigenvalue study, the eigenvalue solver produced an Input/Output Error. Does anyone have suggestions on how to go about troubleshooting this error?

-Model Information: The model is of a MEMS device that consists of a thin plate attached to a substrate by 4 springs. The parameter being changed by the sweep is the width of the springs.

-Setup Information: Using Comsol version 4.2a on a linux computer running Ubuntu.

-Attempted Solution: Based off the error title, I thought it might be a memory issue. I tried switching solvers from MUMPS to PARDISO (I've heard PARDISO is more memory efficient).


Thanks,
Josh

4 Replies Last Post 18.10.2012, 19:29 GMT-4
COMSOL Moderator

Hello Joshua Bauer

Your Discussion has gone 30 days without a reply. If you still need help with COMSOL and have an on-subscription license, please visit our Support Center for help.

If you do not hold an on-subscription license, you may find an answer in another Discussion or in the Knowledge Base.


Please login with a confirmed email address before reporting spam

Posted: 1 decade ago 04.10.2012, 10:19 GMT-4
Did u figure out the reason behind this error ???
Thanks in advance

Regards,
Mohamed
Did u figure out the reason behind this error ??? Thanks in advance Regards, Mohamed

Please login with a confirmed email address before reporting spam

Posted: 1 decade ago 04.10.2012, 11:51 GMT-4
What is exactly the Input/Output Error message?
--
Felipe
What is exactly the Input/Output Error message? -- Felipe

Please login with a confirmed email address before reporting spam

Posted: 1 decade ago 18.10.2012, 11:33 GMT-4
hello, has anyone figured it yet. ??
hello, has anyone figured it yet. ??

Please login with a confirmed email address before reporting spam

Posted: 1 decade ago 18.10.2012, 19:29 GMT-4
Our problem was that the recovery files that COMSOL creates in the directory .comsol in your home directory were overfilling our disk quota. The solution we used was to make a directory in an area with much more memory, then we soft-linked the .comsol directory in the home area to the directory in the area with more space (if you don't know, a soft link is sort of like a pointer to another directory- read www.thegeekstuff.com/2010/10/linux-ln-command-examples/ if you want more detail). This made it so that when Comsol tried to write to the .comsol directory in the home area, the data actually went to a directory with much more space. Hope this helps!
Our problem was that the recovery files that COMSOL creates in the directory .comsol in your home directory were overfilling our disk quota. The solution we used was to make a directory in an area with much more memory, then we soft-linked the .comsol directory in the home area to the directory in the area with more space (if you don't know, a soft link is sort of like a pointer to another directory- read http://www.thegeekstuff.com/2010/10/linux-ln-command-examples/ if you want more detail). This made it so that when Comsol tried to write to the .comsol directory in the home area, the data actually went to a directory with much more space. Hope this helps!

Note that while COMSOL employees may participate in the discussion forum, COMSOL® software users who are on-subscription should submit their questions via the Support Center for a more comprehensive response from the Technical Support team.