bug message reminder

When adressing a model crash or bug, please remember to include an entire model setup in your post that reproduces the crash or exposes the bug. Also add the XBlog.txt file. This is necessary information for people that are trying to help you. Including your model setup can be achieved by adding the zipped run directory (excluding output) as an attachment to the post.


error: severe (40): recursive I/O operation, unit 98, file unknown

Anna Kroon, modified 1 Year ago.

error: severe (40): recursive I/O operation, unit 98, file unknown

Capillary Posts: 1 Join Date: 4/20/12 Recent Posts

Hi all,


I have compiled xbeach for Linux following the steps described in the post https://oss.deltares.nl/web/xbeach/forum/-/message_boards/view_message/1003831.

When trying to run xbeach (either with or without mpi) I get the following "error: severe (40): recursive I/O operation, unit 98, file unknown".

If I look in the source code this seems to be related to writing the log file. I have checked writing rights.

Is there anyone who knows how to resolve this problem?





Dennis Kemp, modified 12 Days ago.

RE: error: severe (40): recursive I/O operation, unit 98, file unknown

Capillary Posts: 1 Join Date: 1/8/20 Recent Posts
The normal arrangement is utilizing the underlying working memory file system approach where a two-organize boot is performed where a little miniaturized scale working framework is stacked first which stacks the modules and afterward moves control to the genuine working framework which has the modules. With a self-gathered piece commonly you can simply order those modules worked in light of the fact that you realize you need them and they will consistently continue running and never be emptied in any case so it's smarter to assemble them in regardless, enabling you to not have an underlying working memory working online essay writers framework which again incredibly accelerates the boot. ake the BFQ scheduler, it's test and not mainlined at this point however every benchmark basically exhibits it is just put for almost every case the best scheduler, both throughput and startup times are better than all other I/O schedulers on both turning plates and strong state drives. Another mainstream most loved are things like kdbus, the BFS CPU scheduler and other out-of-tree stuff that need individual assemblage commonly to utilize. Regularly you have to assemble it yourself also to furnish yourself with gr security.