System information
| Type |
Version/Name |
| Distribution Name |
Debian |
| Distribution Version |
13 (trixie) |
| Kernel Version |
6.12.57+deb13-amd64 |
| Architecture |
amd64 |
| OpenZFS Version |
zfs-2.3.2-2, zfs-kmod-2.3.2-2 |
Describe the problem you're observing
When running zpool status -j to format the output as JSON, draid vdevs are missing the keys vdev_type and state, which (most?) other vdev types have. This information is available for draid vdevs when not formatting as JSON.
Describe how to reproduce the problem
Run zpool status and zpool status -j on a pool with a draid vdev and compare the output.
Include any warning/errors/backtraces from the system logs
System information
Describe the problem you're observing
When running
zpool status -jto format the output as JSON,draidvdevs are missing the keysvdev_typeandstate, which (most?) other vdev types have. This information is available fordraidvdevs when not formatting as JSON.Describe how to reproduce the problem
Run
zpool statusandzpool status -jon a pool with adraidvdev and compare the output.Include any warning/errors/backtraces from the system logs