Afternoon,
The panic looks due to the fact that your SVM state databases aren't
all there, so when we came to update one of them we found there
was <= 50% of the state databases and crashed.
This doesn't look like anything to do with ZFS.
I'd check the output from metadb and see if it looks like
you've got a SVM database on a disk that's also in use by ZFS.
Jan 23 18:50:36 newponit SCSI transport failed: reason 'timeout':
giving up
Jan 23 18:50:36 newponit md: [ID 312844 kern.warning] WARNING: md:
state
database commit failed
Jan 23 18:50:36 newponit last message repeated 1 time
Jan 23 18:51:38 newponit unix: [ID 836849 kern.notice]
Jan 23 18:51:38 newponit ^Mpanic[cpu2]/thread=30000e81600:
Jan 23 18:51:38 newponit unix: [ID 268973 kern.notice] md: Panic
due to
lack of DiskSuite state
Jan 23 18:51:38 newponit database replicas. Fewer than 50% of the
total
were available,
Jan 23 18:51:38 newponit so panic to ensure data integrity.
Regards,
Jason
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
