> From: Arne Jansen [mailto:sensi...@gmx.net] > > Edward Ned Harvey wrote: > > Due to recent experiences, and discussion on this list, my colleague > and > > I performed some tests: > > > > Using solaris 10, fully upgraded. (zpool 15 is latest, which does > not > > have log device removal that was introduced in zpool 19) In any way > > possible, you lose an unmirrored log device, and the OS will crash, > and > > the whole zpool is permanently gone, even after reboots. > > > > I'm a bit confused. I tried hard, but haven't been able to reproduce > this > using Sol10U8. I have a mirrored slog device. While putting it > under load doing synchronous file creations, we pulled the power cords > and unplugged the slog devices. After powering on zfs imported the > pool, > but prompted to acknowledge the missing slog devices with zpool clear. > After that the pool was accessible again. That's exactly how it should > be.
Very interesting. I did this test some months ago, so I may not recall the relevant details, but here are the details I do remember: I don't recall if I did this test on osol2009.06, or sol10. In Sol10u6 (and I think Sol10u8) the default zpool version is 10, but if you apply all your patches, then 15 becomes available. I am sure that I've never upgraded any of my sol10 zpools higher than 10. So it could be that an older zpool version might exhibit the problem, and you might be using a newer version. In osol2009.06, IIRC, the default is zpool 14, and if you upgrade fully, you'll get to something around 24. So again, it's possible the bad behavior went away in zpool 15, or any other number from 11 to 15. I'll leave it there for now. If that doesn't shed any light, I'll try to dust out some more of my mental cobwebs. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
