llnl / llnl/UnifyFS

Intel Fortran compiler errors out on unifycr file descriptors

Open
#300 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
122
Forks
34
PR merge metrics
No merged PRs in 30d

Description

With the Intel Fortran compiler, I get the following:

```
+ test_write
forrtl: Bad file descriptor
forrtl: severe (108): cannot stat file, unit 0, file /unifycr/file.ckpt
Image PC Routine Line Source
test_write 000000000040B0CE for__io_return Unknown Unknown
test_write 000000000041A0C5 for_open Unknown Unknown
test_write 0000000000408A51 Unknown Unknown Unknown
test_write 000000000040866E Unknown Unknown Unknown
libc-2.17.so 00002AAAAC09D3D5 __libc_start_main Unknown Unknown
test_write 0000000000408569 Unknown Unknown Unknown
```

I was able to see that this was in fact running through the UnifyCR I/O wrappers. The for_open was eventually calling into the open64 wrapper. It's possible that the Intel Fortran I/O library may not like the out-of-range file descriptor the wrapper is returning.

### System information

Type | Version/Name
--- | ---
Operating System |
OS Version |
Architecture |
UnifyCR Version |

### Describe the problem you're observing

### Describe how to reproduce the problem

### Include any warning or errors or releveant debugging data

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the UnifyFS open64 wrapper reached from Intel Fortran's for_open and reproduce the reported Bad file descriptor error with the available test_write case. Compare the descriptor returned by the wrapper with Intel Fortran's expectations; done means the Fortran file open succeeds without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, fortran
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.