On 2013-02-20 23:49, Markus Grundmann wrote:
add an pool / filesystem property as an additional security layer for
administrators.
Whenever I modify zfs pools or filesystems it's possible to destroy [on
a bad day :-)] my data. A new
property protected=on|off in the pool and/or filesystem can
Richard Elling richard.ell...@gmail.com wrote:
On Feb 20, 2013, at 3:27 PM, Tim Cook t...@cook.ms wrote:
On Wed, Feb 20, 2013 at 5:09 PM, Richard Elling richard.ell...@gmail.com
wrote:
On Feb 20, 2013, at 2:49 PM, Markus Grundmann mar...@freebsduser.eu wrote:
My name is Markus and I
Moin Fabian :-)
I think the zfs allow|deny feature is only for filesystems. I wish me
a feature to protect the complete pool. The property is restricted to
zpool commands.
On my notebook I have created a pool with simulated drives
(gpt/drive1..n) and without any warnings or you are sure
Hi Markus,
On Thu, Feb 21, 2013 at 6:44 AM, Markus Grundmann mar...@freebsduser.eu wrote:
I think the zfs allow|deny feature is only for filesystems. I wish me a
feature to protect the complete pool. The property is restricted to zpool
commands.
On my notebook I have created a pool with
On 02/21/2013 03:34 PM, Jan Owoc wrote:
Does this do what you want? (zpool destroy is already undo-able) Jan
Jan that's not was I want.
I want set a property that's enable/disable all modifications with zpool
commands (e.g. zfs destroy, zfs detach ...)
This property is also possible for zfs
On 02/21/2013 04:02 PM, Markus Grundmann wrote:
On 02/21/2013 03:34 PM, Jan Owoc wrote:
Does this do what you want? (zpool destroy is already undo-able) Jan
Jan that's not was I want.
I want set a property that's enable/disable all modifications with zpool
commands (e.g. zfs destroy, zfs
On Thu, Feb 21, 2013 at 8:34 AM, Jan Owoc jso...@gmail.com wrote:
Hi Markus,
On Thu, Feb 21, 2013 at 6:44 AM, Markus Grundmann mar...@freebsduser.eu
wrote:
I think the zfs allow|deny feature is only for filesystems. I wish me a
feature to protect the complete pool. The property is
It's anyone here on the list that's have some tips for me what files are
to modify ? :-)
In my current source tree now is a new property PROTECTED available
both for pool- und zfs-objects. I have also two functions added to
get and set the property above. The source code tree is very big and
On 2013-02-21 16:54, Markus Grundmann wrote:
It's anyone here on the list that's have some tips for me what files are
to modify ? :-)
In my current source tree now is a new property PROTECTED available
both for pool- und zfs-objects. I have also two functions added to
get and set the property
On Wed, Feb 20, 2013 at 4:49 PM, Markus Grundmann mar...@freebsduser.euwrote:
Hi!
My name is Markus and I living in germany. I'm new to this list and I have
a simple question
related to zfs. My favorite operating system is FreeBSD and I'm very happy
to use zfs on them.
It's possible to
Hi Markus,
On Wed, Feb 20, 2013 at 3:49 PM, Markus Grundmann mar...@freebsduser.eu wrote:
It's possible to enhance the properties in the current source tree with an
entry like protected?
I find it seems not to be difficult but I'm not an professional C
programmer. For more information
please
On Wed, Feb 20, 2013 at 4:49 PM, Markus Grundmann mar...@freebsduser.eu wrote:
Whenever I modify zfs pools or filesystems it's possible to destroy [on a
bad day :-)] my data. A new
property protected=on|off in the pool and/or filesystem can help the
administrator for datalost
(e.g. zpool
On Feb 20, 2013, at 2:49 PM, Markus Grundmann mar...@freebsduser.eu wrote:
Hi!
My name is Markus and I living in germany. I'm new to this list and I have a
simple question
related to zfs. My favorite operating system is FreeBSD and I'm very happy to
use zfs on them.
It's possible to
Am 21.02.2013 00:02, schrieb Tim Cook:
I think you're underestimating your English, it's quite good :)
Thank you Tim :-)
In any case, I think the proposal is a good one. With the default
behavior being off, it won't break anything for existing datasets, and
it can absolutely help prevent a
Am 21.02.2013 00:08, schrieb Mike Gerdts:
On Wed, Feb 20, 2013 at 4:49 PM, Markus Grundmann mar...@freebsduser.eu wrote:
Whenever I modify zfs pools or filesystems it's possible to destroy [on a
bad day :-)] my data. A new
property protected=on|off in the pool and/or filesystem can help the
Look at the delegable properties (zfs allow). For example, you can
delegate a user to have
specific privileges and then not allow them to destroy.
Note: I'm only 99% sure this is implemented in FreeBSD, hopefully
someone can verify.
-- richard
Hi Richard!
I think it's implemented but
On Wed, Feb 20, 2013 at 5:09 PM, Richard Elling richard.ell...@gmail.comwrote:
On Feb 20, 2013, at 2:49 PM, Markus Grundmann mar...@freebsduser.eu
wrote:
Hi!
My name is Markus and I living in germany. I'm new to this list and I have
a simple question
related to zfs. My favorite operating
On Feb 20, 2013, at 3:27 PM, Tim Cook t...@cook.ms wrote:
On Wed, Feb 20, 2013 at 5:09 PM, Richard Elling richard.ell...@gmail.com
wrote:
On Feb 20, 2013, at 2:49 PM, Markus Grundmann mar...@freebsduser.eu wrote:
Hi!
My name is Markus and I living in germany. I'm new to this list and I
On Wed, Feb 20, 2013 at 6:47 PM, Richard Elling richard.ell...@gmail.comwrote:
On Feb 20, 2013, at 3:27 PM, Tim Cook t...@cook.ms wrote:
On Wed, Feb 20, 2013 at 5:09 PM, Richard Elling
richard.ell...@gmail.comwrote:
On Feb 20, 2013, at 2:49 PM, Markus Grundmann mar...@freebsduser.eu
On 02/21/2013 02:59 AM, Tim Cook wrote:
I hear you, but in his scenario of using scripts for management, there
isn't necessarily human interaction to confirm the operation
(appropriately or not). Having a pool property seems like an easy way
to prevent a mis-parsed or outright incorrect
20 matches
Mail list logo
