Visual Fortran run-time error (38)

Author	Message
old_user298 Send message Joined: 6 Aug 04 Posts: 5 Credit: 1,818,345 RAC: 0	Message 21420 - Posted: 19 Mar 2006, 10:43:08 UTC For what it\'s worth, received this error. Everything seems okay, though not entirely sure. Having read other forum posts, machine stability not an issue, so perhaps it was a software hiccup? --------------------------- Visual Fortran run-time error --------------------------- forrtl: severe (38): error during write, unit 8, file E:\\BOINC\\projects\\climateprediction.net\\hadcm3lb_4vqr_05015743\\tmp\\pipe_dummy Image PC Routine Line Source hadcm3transum_5.0 006EC5BA Unknown Unknown Unknown hadcm3transum_5.0 006E983C Unknown Unknown Unknown hadcm3transum_5.0 0069AFCC Unknown Unknown Unknown hadcm3transum_5.0 0069B47E Unknown Unknown Unknown hadcm3transum_5.0 00683B61 Unknown Unknown Unknown hadcm3transum_5.0 004111A5 Unknown Unknown Unknown hadcm3transum_5.0 00407084 Unknown Unknown Unknown kernel32.dll 7C816D4F Unknown Unknown Unknown --------------------------- OK --------------------------- ID: 21420 · Reply Quote

Les Bayliss Volunteer moderator Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0	Message 21421 - Posted: 19 Mar 2006, 11:36:03 UTC Carl posted the following yesterday: the pipe/tmp_dummy write error is usually a disk problem; could even be running out of disk space, but usually it means a disk error has cropped up. And the unified model, being the unforgiving thing it is, just crashes immediately upon a disk error. ID: 21421 · Reply Quote

MikeMarsUK Volunteer moderator Send message Joined: 13 Jan 06 Posts: 1498 Credit: 15,613,038 RAC: 0	Message 21422 - Posted: 19 Mar 2006, 12:50:50 UTC Is there anything unusual about your filesystem, perhaps raid, network drive, USB external drive, ... ? I'm a volunteer and my views are my own. News and Announcements and FAQ ID: 21422 · Reply Quote

paul Send message Joined: 22 Mar 06 Posts: 1 Credit: 10,948,802 RAC: 7,475	Message 21517 - Posted: 23 Mar 2006, 2:45:53 UTC - in response to Message 21421. Carl posted the following yesterday: the pipe/tmp_dummy write error is usually a disk problem; could even be running out of disk space, but usually it means a disk error has cropped up. And the unified model, being the unforgiving thing it is, just crashes immediately upon a disk error. I got a similar error. The file was 0 bytes. The disk has 13.4 GB of free space. This is the only program I\'ve ever gotten a disk error and I run many Visual Fortran programs. Should I get rid of it? or is it correcting itself? ID: 21517 · Reply Quote

old_user21637 Send message Joined: 28 Sep 04 Posts: 36 Credit: 268,150 RAC: 0	Message 24275 - Posted: 12 Sep 2006, 3:53:36 UTC - in response to Message 21420. Last modified: 12 Sep 2006, 4:07:45 UTC For what it\'s worth, received this error. Everything seems okay, though not entirely sure. Having read other forum posts, machine stability not an issue, so perhaps it was a software hiccup? --------------------------- Visual Fortran run-time error --------------------------- forrtl: severe (38): error during write, unit 8, file E:\\BOINC\\projects\\climateprediction.net\\hadcm3lb_4vqr_05015743\\tmp\\pipe_dummy Image PC Routine Line Source hadcm3transum_5.0 006EC5BA Unknown Unknown Unknown hadcm3transum_5.0 006E983C Unknown Unknown Unknown hadcm3transum_5.0 0069AFCC Unknown Unknown Unknown hadcm3transum_5.0 0069B47E Unknown Unknown Unknown hadcm3transum_5.0 00683B61 Unknown Unknown Unknown hadcm3transum_5.0 004111A5 Unknown Unknown Unknown hadcm3transum_5.0 00407084 Unknown Unknown Unknown kernel32.dll 7C816D4F Unknown Unknown Unknown --------------------------- OK --------------------------- I\'ve got the same problem. This error only appears when I am running an application I am developing for my Phd. It is an intensive mathematical computation application, that also uses the PThreads for Win32 library. So I believe this error is caused by either something related to the coprocessor or (more probably) to some peculiar interaction with the pthreads for Win32 for C++ library. Of course, since my application is computation intensive, I am simply stopping BOINC while running it. It would be interested though to know what causes this error. I agree, it is definitely NOT related to disk space or some hardware problem, it is CPDN or BOINC being influenced somehow by some other piece of software. Cheers, Stefan. ID: 24275 · Reply Quote