zpool: use tab to intend continuation from removal status

[ThomasLamprecht]

Bring the output of the removal status in line with the other
"fields" that zpool status outputs, and thus allows an parser to
easier detect this as continuation of the 'remove:' output.

Before:

remove: Removal of vdev 0 copied 282G in 0h9m, completed on [...]
    776K memory used for removed device mappings

Now:

remove: Removal of vdev 0 copied 282G in 0h9m, completed on [...]
	776K memory used for removed device mappings

Signed-off-by: Thomas Lamprecht [email protected]

Motivation and Context

We have a parser for the zpool status output which uses the fact that continuations of output values over multiple lines uses a tab to intend those continuations, allowing detecting them relatively easily.
We got a report of a failure in said parser and when checking the offending zpool status output we saw that the removal status is not tab intended but used four space-characters, and was not covered by our testcases.

After checking zpool status print code I figured this change would fit in and allow us to avoid special handling in the now relatively simple and general parser.

Description

Switch four spaces with a tab in two instances.

How Has This Been Tested?

Created a pool with a mirror, added an extra mirror and removed it again resulting in triggering the removal status code to print,
compared the output before and after.

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)

Note, this can be probably seen as bug fix only in the widest sense, so please do not take above marking as such to serious.

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.

[behlendorf]

Thanks!