Right, the disk that crashed had an unmirrored swap partition. So it's completely clear, that non_persist could becomet corrupted. svc.configd crashed some seconds after the first hardware error for the particular disk was reported. So far so good.
But a way to switch SMF back to consistent state without rebooting the system is IMHO highly desirable. I mean a single temporary file (which is a compilation of some xml-files which are placed safely on a mirrored fs) shouldn't cause such consequences. I think the reason for requiring a reboot is the limited abilities to "restart" the SMF system. It seems that it cannot handle this situation very well (maintenance or uninitialized state for services that are fully operatice). Is svc.configd's core of any use for you? Thanks, HJ This message posted from opensolaris.org
