Hi
But we won't use the zpool type ever again. Its just not worth it.
Here's what happened:
. one of our servers lost knowledge about one of its zfs pools
. puppet didn't find the pool and .. went on to zpool create it
. we did indeed have a backup, but would have lost all data if not
Creating zpools is a manual thing in every case, since one has to
know the devices participating. The names of which tend to be a
little bit different from one server to the next.
Add that to the possibility of major data loss (like we just
experienced) and get a negative yield for the 'zpool' type.
there was recently a similar discussion about that with the new
available fs and lvm type on the puppet-dev list. these are indeed
very dangerous operations, where it should somehow be possible to lock
them. the problem is clearly that if puppet fails to determine the
correct state it tries to transfer into the right state, which might
have (obviously) - ehhh - "nasty side-effects" on such operations.
maybe you can catch that discussion up and give your thoughts about it
how puppet should behave and how it would be possible to "lock" such
operations.
cheers pete
--
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.
