https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232671
--- Comment #4 from Conrad Meyer <c...@freebsd.org> --- Oh, and one more thing to consider: gmirror is really aggressive about destroying itself when it gets into a bad state. That might not be the best thing for resiliency, even if all mirrors are dead? I.e. it could stay alive and ENXIO or EIO all IO and wait for an administrator to add or remove disks (or administratively kill it). This is mostly orthogonal to this bug, except I'd like gmirror's self-destruct function to log much more explicitly than it does today. The only hint we have during the boot process is: "root_mount_rel[2352] 0xppppppp", and that only because we have GEOM debugging level 1 enabled! If a CAM device dies and removes itself, you bet the console hears about it. Just my 2ยข. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-geom@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscr...@freebsd.org"
