fs.mkdirSync with `recursive: true` throws ENOENT instead of ENOSPC when disk is full

### Version

16.14.1

### Platform

Linux

### Subsystem

_No response_

### What steps will reproduce the bug?

_No response_

### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior?

Same as `fs.mkdirSync` without options:

```js
> fs.mkdirSync('./a')
Uncaught Error: ENOSPC: no space left on device, mkdir './a'
    at Object.mkdirSync (node:fs:1336:3) {
  errno: -28,
  syscall: 'mkdir',
  code: 'ENOSPC',
  path: './a'
}
```

### What do you see instead?

```js
> fs.mkdirSync('./a', {recursive: true})
Uncaught Error: ENOENT: no such file or directory, mkdir './a'
    at Object.mkdirSync (node:fs:1336:3) {
  errno: -2,
  syscall: 'mkdir',
  code: 'ENOENT',
```
### Additional information

_No response_

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Sponsors

Uh oh!

fs.mkdirSync with `recursive: true` throws ENOENT instead of ENOSPC when disk is full #42808

Version

Platform

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Participants

fs.mkdirSync with recursive: true throws ENOENT instead of ENOSPC when disk is full #42808

Description

Version

Platform

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Participants

Issue actions

fs.mkdirSync with `recursive: true` throws ENOENT instead of ENOSPC when disk is full #42808