[sandy]

Hi foamers,

When I run "decomposePar" to my case, I got error stories again as follow:

--> FOAM FATAL ERROR:

Couldn't creat directory "/home/user/OpenFOAM/user-1.6.x/tutorials/multiphase/interPhaseChangeFoam/cavitatingBullet/processor1"

From function Foam::mkDir(const fileName&, mode_t)
in file POSIX.C at line 423.FOAM exiting


I check the POSIX.C file at line 423, the code were written as follows:

default:
{
FatalErrorIn("Foam::mkDir(const fileName&, mode_t)")
<< "Couldn't create directory " << pathName
<< exit(FatalError);

return false;
}


What is wrong with it? Who can help me out? Thanks.

Sandy

[wyldckat]

Greetings Sandy,

Have you tried making the directory manually? There might already be a file named "processor1" or you might have reduced permissions on the case folder, for some strange reason...

So, try this:

mkdir /home/user/OpenFOAM/user-1.6.x/tutorials/multiphase/interPhaseChangeFoam/cavitatingBullet/processor1

If that also gives an error, than try:

ls -la /home/user/OpenFOAM/user-1.6.x/tutorials/multiphase/interPhaseChangeFoam/cavitatingBullet/

If that also gives out and error saying "not found", than there might be some misconfiguration somewhere... like for example:

• your user name in your Linux box isn't "user", and for some reason, the environment variables got mixed when defined by the bashrc script at $HOME/OpenFOAM/OpenFOAM-1.6.x/etc;
• the file decomposeParDict (if I'm not mistaken) has the address to the case folder mistyped;
• you might have launched decomposePar with the -case argument, and didn't provide the correct address.

Now, in case the command ls -la does give you a list of files and folders, check for the existence of a file or folder processor1, or check the permissions and ownership of the files and folders present there.

Additionally, in case you edited out your true user name and put in "user", it could be due to your user name having special characters or spaces in the name, thus making OpenFOAM to throw an error... although in Linux that shouldn't be an issue.

Best regards,
Bruno Santos

[sandy]

Originally Posted by wyldckat

Greetings Sandy,

Have you tried making the directory manually? There might already be a file named "processor1" or you might have reduced permissions on the case folder, for some strange reason...

So, try this:

mkdir /home/user/OpenFOAM/user-1.6.x/tutorials/multiphase/interPhaseChangeFoam/cavitatingBullet/processor1

If that also gives an error, than try:

ls -la /home/user/OpenFOAM/user-1.6.x/tutorials/multiphase/interPhaseChangeFoam/cavitatingBullet/

If that also gives out and error saying "not found", than there might be some misconfiguration somewhere... like for example:

• your user name in your Linux box isn't "user", and for some reason, the environment variables got mixed when defined by the bashrc script at $HOME/OpenFOAM/OpenFOAM-1.6.x/etc;
• the file decomposeParDict (if I'm not mistaken) has the address to the case folder mistyped;
• you might have launched decomposePar with the -case argument, and didn't provide the correct address.

Now, in case the command ls -la does give you a list of files and folders, check for the existence of a file or folder processor1, or check the permissions and ownership of the files and folders present there.

Additionally, in case you edited out your true user name and put in "user", it could be due to your user name having special characters or spaces in the name, thus making OpenFOAM to throw an error... although in Linux that shouldn't be an issue.

Best regards,
Bruno Santos

If that, sir, how and when I can get the passport, you think?

[Ahmed]

Your error message, openfoam cannot create a directory, and Bruno Santos is telling you to create this folder manually and see what is wrong there

[sandy]

WOW, it is amazing ... I solved them! Thanks, anyway...

[Ahmed]

Lee
I do not read private messages, you have anything to say, say it here.
Again, the openfoam error message is very clear, the programme cannot create the folder, see why

[sandy]

Originally Posted by Ahmed

Lee
I do not read private messages, you have anything to say, say it here.
Again, the openfoam error message is very clear,

Hi Ahmed, Children can not know even simple words, Who can teach them, you think?

Originally Posted by Ahmed

the programme cannot create the folder, see why

Why? ..

[wyldckat]

Hi Sandy,

Can you run:

ls -la /home/user/OpenFOAM/user-1.6.x/tutorials/multiphase/interPhaseChangeFoam/cavitatingBullet/

And post the output here?

Best regards,
Bruno

[tjliang]

Originally Posted by sandy

Hi foamers,

When I run "decomposePar" to my case, I got error stories again as follow:

--> FOAM FATAL ERROR:

Couldn't creat directory "/home/user/OpenFOAM/user-1.6.x/tutorials/multiphase/interPhaseChangeFoam/cavitatingBullet/processor1"

From function Foam::mkDir(const fileName&, mode_t)
in file POSIX.C at line 423.FOAM exiting


I check the POSIX.C file at line 423, the code were written as follows:

default:
{
FatalErrorIn("Foam::mkDir(const fileName&, mode_t)")
<< "Couldn't create directory " << pathName
<< exit(FatalError);

return false;
}


What is wrong with it? Who can help me out? Thanks.

Sandy

Helli Sandy,

I have now the same problem with you and it also runs in parallel, coule you please tell me what's wrong with that?

Best Regards,

Peng

[Alhasan]

Hello All,

My simulations have been suddenly crashing with the following error and these are very expensive simulations on the cluster and I have no idea what is making them crash with this error any suggestions, they run well for a week or so and they then crash

[10] 
[10] 
[10] 
[10] --> FOAM FATAL ERROR: 
[10] Couldn't create directory "/panfs/panasas01/aero/mk14466/WorkSpace/5.5Deg-Ref-DynSmag/processor10/0.0578987"
[10] 
[10]     From function Foam::mkDir(const fileName&, mode_t)
[10]     in file POSIX.C at line 555.
[10] 
FOAM parallel run exiting
[10] 
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 10 in communicator MPI_COMM_WORLD 
with errorcode 1.

Thanks for your help,
Hasan K.J

[Eslam Reda]

It is a disk size issue, free some space for the new files