kern/60900: RAIDframe: autoconfiguration loses spares

["tls%panix.com@localhost via gnats" <gnats-admin%NetBSD.org@localhost>]

>Number:         60900
>Category:       kern
>Synopsis:       Autoconfigured RAID sets lose their spares at the first reboot.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Oct 18 16:15:00 +0000 2026
>Originator:     Thor Lancelot Simon
>Release:        NetBSD 11.0
>Organization:
>Environment:
	
	
System: NetBSD panix5.panix.com 11.0 NetBSD 11.0 (PANIX-WEBUSER) #0: Mon Oct 5 15:33:08 EDT 2026 root%juggler.panix.com@localhost:/misc/obj64/misc/devel/netbsd/11.0/src/sys/arch/amd64/compile/PANIX-WEBUSER amd64
Architecture: x86_64
Machine: amd64
>Description:
	When a RAID set is configured with one or more spares (via
	config file or via raidtl -a), RAID autoconfiguration
	loses the spares at the first reboot.  A related issue
	is that despite the documentation and code comments,
	even if a spare is available, a degraded set does not
	automatically reconstruct.  It also appears from code
	inspection that there are numerous minor bugs in the
	logic for handling spares and reconstruction, including
	an aparrent vnode leak when removing a spare, loss of
	the partition size of the spare if it differs from
	(exceeds that) of the replaced component, and racy
	handling of the in-memory reconstruction flag.
>How-To-Repeat:
	Configure a RAID set with a spare; ensure it is
	properly labelled and initialized; set it for
	autoconfiguration.  Reboot the system and observe
	the spare is nowhere to be seen in the running
	configuration.
>Fix:
	

>Unformatted: