zdb raidz file layout

[don-brady]

Motivation and Context

It would be nice to be able to visualize how the RAIDZ disk columns for a given file are laid out on disk. For example, one might ponder if the parity is being evenly distributed or are the same disks being used for parity?

Description

This change introduces the --file-layout (-f) option to zdb(8) to display the raidz file layout for a given file. The change leverages the vdev_raidz_map_alloc() function to find the map of how the block data is laid out across the child disks.

A typical column entry looks like:

┌────────────┐
│  D2     43 │
│     6020da │
└────────────┘

Which here represents the logical data column 2 that is 43 sectors high starting at sector 0x6020da. The parity is displayed in inverse text if output is to a terminal (see example below).

Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.

An example

How Has This Been Tested?

Tested with various flavors of raidz and disk counts.
Tested with ZTS cli_root/zdb suite of tests.

Known Issues/Limitations

1. Only supports RAIDZ. A follow-on pull request can add support for dRAID.
2. The check for the last row is not always correct and so the edge connector, like '├', can sometimes show final connector '└' by mistake.
3. Only supports one top-level RAIDZ

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.