View Issue Details

IDProjectCategoryView StatusLast Update
0000358OpenFOAMBugpublic2011-12-23 12:09
Reportermonto Assigned Touser4 
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
PlatformLinuxOSCentOSOS Version5.5 x86_64
Summary0000358: IOstream error when using directMappedPatch in parallel
DescriptionWhen running a decomposed case that uses a directMapped patch on the inlet, depending on the decomposition pattern, an IOstream error is issued:



Starting time loop

Reading/calculating field UMean

Reading/calculating field pMean

Reading/calculating field UPrime2Mean

Reading/calculating field pPrime2Mean

fieldAverage: starting averaging at time 0

Reading surface description:
    nearWall

Time = 1e-05

Courant Number mean: 8.05286e-05 max: 0.05
[2]
[2]
[2] --> FOAM FATAL IO ERROR:
[2] error in IOstream "IOstream" for operation operator>>(Istream&, LList<LListBase, T>&)
[2]
[2] file: IOstream at line 0.
[2]
[2] From function IOstream::fatalCheck(const char*) const
[2] in file db/IOstreams/IOstreams/IOstream.C at line 114.
[2]
FOAM parallel run exiting
[2]
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 2 in communicator MPI_COMM_WORLD
with errorcode 1.
Steps To Reproduce1. Modify the pitzDailyDirectMapped tutorial to make it fully 3D (change number of cells in Z direction from 1 to 10 and side patches to 'symmetryPlane').

2. Decompose with method "scotch" and a number of subdomains greather than 12

3. mpirun -np <> pisoFoam -parallel

Additional Informationif the same case is run on a workstation (OpenSuse 11.4, Intel Core i7), with an even higher number of decomposed domains, the solver starts fine and no error is issued.

The error seems irrespective of the openmpi version used.
TagsNo tags attached.

Activities

monto

2011-12-15 15:07

reporter  

user4

2011-12-23 12:09

  ~0000869

fixed in

385a0d77d15fdab942a33296f6e17ba1e8a2e9f4 (2.1.x)
2342dcb20364442bfe67555356eb5b9ba6d6bf9b (2.0.x)

Thanks for reporting.

Issue History

Date Modified Username Field Change
2011-12-15 15:07 monto New Issue
2011-12-15 15:07 monto File Added: pitzDailyDirectMapped.tgz
2011-12-23 12:09 user4 Note Added: 0000869
2011-12-23 12:09 user4 Status new => resolved
2011-12-23 12:09 user4 Fixed in Version => 2.1.x
2011-12-23 12:09 user4 Resolution open => fixed
2011-12-23 12:09 user4 Assigned To => user4