In message <7f44e458-5d27-42b6-ac81-7f4ff61d6...@gmail.com>, Richard Elling wri
tes:
>The iSCSI service is not STMF. STMF will need to be disabled, or the =
>volume no longer
>used by STMF.
>
>iSCSI service is svc:/network/iscsi/target:default
>STMF service is svc:/system/stmf:default
Thank you fo
On Feb 21, 2013, at 8:02 AM, John D Groenveld wrote:
> # zfs list -t vol
> NAME USED AVAIL REFER MOUNTPOINT
> rpool/dump4.00G 99.9G 4.00G -
> rpool/foo128 66.2M 100G16K -
> rpool/swap4.00G 99.9G 4.00G -
>
> # zfs destroy rpool/foo128
> cannot destroy 'rpool/fo
On 2013-02-21 17:02, John D Groenveld wrote:
# zfs list -t vol
NAME USED AVAIL REFER MOUNTPOINT
rpool/dump4.00G 99.9G 4.00G -
rpool/foo128 66.2M 100G16K -
rpool/swap4.00G 99.9G 4.00G -
# zfs destroy rpool/foo128
cannot destroy 'rpool/foo128': volume is busy
C
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 pro
I have come up against a common problem (Most recently discussed in
thread titled "cannot replace X with Y: devices have different sector
alignment"), and have to do a " zfs send -R ... | zfs recv ..." to
migrate from old to new disks.
While searching I saw reference to a new feature being dis
# zfs list -t vol
NAME USED AVAIL REFER MOUNTPOINT
rpool/dump4.00G 99.9G 4.00G -
rpool/foo128 66.2M 100G16K -
rpool/swap4.00G 99.9G 4.00G -
# zfs destroy rpool/foo128
cannot destroy 'rpool/foo128': volume is busy
I checked that the volume is not a dump or swap d
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 b
On Thu, Feb 21, 2013 at 8:34 AM, Jan Owoc wrote:
> Hi Markus,
>
> On Thu, Feb 21, 2013 at 6:44 AM, Markus Grundmann
> 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 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
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
Hi Markus,
On Thu, Feb 21, 2013 at 6:44 AM, Markus Grundmann 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 simulated drives (g
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 (
Richard Elling wrote:
> On Feb 20, 2013, at 3:27 PM, Tim Cook wrote:
> > On Wed, Feb 20, 2013 at 5:09 PM, Richard Elling
> > wrote:
> > On Feb 20, 2013, at 2:49 PM, Markus Grundmann wrote:
> >> My name is Markus and I living in germany. I'm new to this list and I have
> >> a simple question
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 h
14 matches
Mail list logo
