[hhm747]

Hello everybody,

I tried to launch an unsteady simulation with initial value on a cluster by cfx161.
but it didn't run and crushed with the following error massage:

Do you know why it says: "file is corrupt"

Thanks
hhm747

An error has occurred in cfx5solve:

Error reported by IO module: recreate_indextable: warning: truncated (or
bad) index data at end of file while rebuilding index, file is corrupt but
probably recoverable, continuing. [1172197824 + 45386 > 1172242432]

An error has occurred in cfx5solve:

Error reported by : write_index: fwrite failed writing format: Bad
file descriptor

An error has occurred in cfx5solve:

Error reported by IO module: iif_flush: write_index failed

An error has occurred in cfx5solve:

Error reported by IO module: cfxwriteString: (fputs failed) syserr:: Bad
file descriptor

[-Maxim-]

I just ran into the same problem and it's driving me crazy. I only have 3 out of your 4 errors:

An error has occurred in cfx5solve:

Error reported by : write_index: fwrite failed writing format: Bad
file descriptor

An error has occurred in cfx5solve:

Error reported by IO module: iif_flush: write_index failed

An error has occurred in cfx5solve:

Error reported by IO module: cfxwriteString: (fputs failed) syserr:: Bad
file descriptor

I use 17.1 and want to solve local parallel on 8 cores.

[-Maxim-]

I reinstalled CFX 17.1, started the job via command line with a different initial condition file and now the error is gone.
My guess is that it was caused by my *.res file that I wanted to use as initial condition.
Will report back if something changes.

[jiaji lu]

Originally Posted by -Maxim-

I reinstalled CFX 17.1, started the job via command line with a different initial condition file and now the error is gone.
My guess is that it was caused by my *.res file that I wanted to use as initial condition.
Will report back if something changes.

Have you solved the probelm? What's th reason?

[-Maxim-]

Originally Posted by jiaji lu

Have you solved the probelm? What's th reason?

Hi,

I don't recall that problem since it occurred to me a few years ago. As I stated in my answer, it might have been caused by a corrupt *.res file.