camcontrol: Support NVMe namespace formatting via the format subcommand

[ken]

Summary

Support formatting NVMe namespaces through the existing format
subcommand rather than a separate nvformat subcommand. The format
subcommand now dispatches on the device protocol, in the same way the
identify and persist subcommands do, and issues the NVMe FORMAT NVM
command for NVMe devices.

The SCSI syntax and behavior are unchanged. The NVMe-specific
options are -e (secure erase setting), -G (format all namespaces),
-f (LBA format), -l (protection information location), -m (metadata
setting) and -p (protection information type). The -q and -y options
work for both protocols; NVMe formats gain the same confirmation
question that SCSI formats have always had. The -r and -w options
are SCSI only; -r returns an error for NVMe devices and -w has no
effect, since the NVMe format command does not complete until the
format is finished.

The default timeout for NVMe is 30 seconds for a cryptographic erase
and 30 minutes otherwise; -T overrides.

sbin/camcontrol/nvformat.c:

New file, the NVMe format backend for the format subcommand.

sbin/camcontrol/camcontrol.c:

Dispatch the format subcommand to scsiformat() or
nvmeformat() based on the device protocol.

sbin/camcontrol/camcontrol.h:

Add the nvmeformat() prototype.

sbin/camcontrol/Makefile:

Add nvformat.c to the build.

sbin/camcontrol/camcontrol.8:

Document NVMe support in the format subcommand section, and
note the differences from SCSI where they occur.

Sponsored by: Spectra Logic

Depends on D59534

Co-Authored-By: Claude Fable 5 <[e-mail]>

[imp]

sbin/camcontrol/camcontrol.c

237

What's NV?
This formats a namespace

Also, why not just format with a protocol selector like we do for identify, sanitize, etc.

sbin/camcontrol/nvformat.c

97

I'd be tempted to rename scsi_get_nv to something that doesn't have scsi in the name, since it's not a scsi thing at all anymore, with backwards compat symbols for a while.

253

I'm pretty sure the extra comments here aren't really helping

[ken]

Rebase on the persist rework in D59534 (the nvres subcommand is gone; no changes to nvformat itself).

[imp]

sbin/camcontrol/nvformat.c

63

Sure this should be NVME_FORMAT_SES_CRYPTO?

253

So I think the timeout is too large. For a crypto format it should be shorter, like 30seconds not 30 minutes.
Otherwise its likely the least sucky thing we can do without a lot of extra code in the kernel.

I ran into this issue in nvmecontrol in https://reviews.freebsd.org/D59828

[ken]

Fix the crypto secure-erase setting to actually map to NVME_FORMAT_SES_CRYPTO (it wrongly mapped to a user data erase), and make the default timeout depend on the erase type: 30 seconds for crypto erase, 30 minutes otherwise. -T still overrides.

[ken]

Rework per the naming discussion: fold NVMe format support into the existing format subcommand (protocol dispatch like identify/persist) and retire nvformat. The NVMe path gains the same are-you-sure confirmation the SCSI path has (-q/-y honored); -r is rejected for NVMe and -w is a no-op since the NVMe format command does not return until the format completes. Tested on hardware: confirmation prompt and abort verified, no formats actually issued.

[ken]

Use the new nvme_ns_data_format_index() from D59627 to determine the current LBA format instead of open-coding the FLBAS extraction, so drives with more than 16 LBA formats get the right default.