Fix "out of memory" error

[behlendorf]

Motivation and Context

#13538 (comment). We're being a bit to aggressive about aborting immediately in zpool_in_use() when the label can't be read. It turns out we can safely relax this. In fact, it's not unlikely that on zpool create a scsi rescan will be triggered when partitioning the device which will resolve the issue.

Description

Drop the no_memory() call from zpool_in_use() when reading the label fails and instead return the error to the caller. This prevents a misleading "internal error: out of memory" error when the label can't be read. This will result in is_spare() returning B_FALSE instead of aborting, which is already safely handled.

Furthermore, on Linux it's possible for EREMOTEIO to returned by an NVMe device if the device has been low-level formatted and not rescanned. In this case we want to fallback to the legacy scanning method and read any of the labels we can.

How Has This Been Tested?

Locally commented out the no_memory() call on a system with an NVMe device returning EREMOTEIO. During zpool create a rescan was correctly triggered when the device was repartitioned resolving the issue.

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.