On Thu, 21 May 2009, Peter Woodman wrote: > Well, it worked for me, at least. Note that this is a very limited > recovery case- it only works if you have the GUID of the slog device from > zpool.cache, which in the case of a fail-on-export and reimport might not > be available. The original author of the fix seems to imply that you can > use any size device as the replacement slog, but I had trouble doing > that. Didn't investigate enough to say conclusively that that is not > possible, though. > > It's a very limited fix, but for the case Paul outlined, it will work, > assuming zpool.cache is available.
Cool, thanks for the info. While if you came across this info after a critical failure it wouldn't be much help, knowing about this beforehand I can make a backup of the cache file stored someplace other than the pool with the slog. I'll have to test it out some, but if it works out it will make me more comfortable about deploying a slog in production. Still haven't heard anything official from Sun support about recovering from this situation. I'm also still really curious why it's so hard to remove a slog, but no one in the know has replied, and that's not the type of question Sun support tends to follow up on :(... -- Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/ Operating Systems and Network Analyst | hen...@csupomona.edu California State Polytechnic University | Pomona CA 91768 _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
