So I don't get how you could have lost your pool, as zpool will refuse to overwrite an existing pool without the "-f". All you would have had to do was run "zpool import<pool>" and you'd been back to normal.
To be perfectly honest with you, I am a bit in the dark about that as well. I've done the same experiment in the meantime - with no success. Guess the pool was really messed up.
Note that I am not telling anyone not to use zpool - it's just not paying off in _my scenario_ anymore. We use large zpools (apart from rootpool) in the big data machines only - and I dont mind doing those manually.
Sure, I could have thought of not having puppet start on system start (as has been suggested elsewhere) - but I must admit that my primary concern was fixing the server ASAP at the time, not what puppet could do to me once the server was back.
That's just something you don't think of there and then... Hence my post. Not wanting to step on anyones toes.
best regards, kaspar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
