----- "Peter Meier" <peter.me...@immerda.ch> a écrit : | | as far as I understood was that the zpool information was lost, hence | puppet thought that there was no zpool anymore. I assume that this | means | that zpool-tools didn't know about that anymore either, but it might | have been recoverable with manual interaction.
Having faced a serious ZFS crash I dug into ZFS internals & design some time ago so I'll permit to drop some thoughs here : the zpool metadata information may be corrupted and pool not to show up. This seems quite bad but there are now tools to rollback over uberblocks (that contain the core data of your pool). Loosing a pool forever is highly unlikely | and looking at the code [1] it doesn't look like it uses -f. I do agree this | in general I see disk allocation as part of provisioning, which | shouldn't go into puppet. but that's how I seperate things and others | might have reasons to do differently. definitively a +1 Nico. -- 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.
