[pve-devel] [PATCH] ZFSPoolPlugin: Added the ability to use nested ZVOLs

[Wolfgang]

There is no need for a flag to do not autoimport, because first you can
disable the storage in storage.cfg.  and so it will not activated. Second
one pool with iscsi export should not in the storage.cfg.
Am 12.02.2015 21:25 schrieb "Pablo Ruiz" <pablo.ruiz at gmail.com>:

> Hi,
>
> IMHO, I see no reason to not default for the most common case (ie.
> auto-importing) if there's a way to override it, and such a way is
> some-what documented.. ;)
>
> On Thu, Feb 12, 2015 at 8:35 PM, Adrian Costin <adrian at goat.fish> wrote:
>
>>
>> AFAIK having a setting to control wether auto-import of pool is desirable
>> would be a plus. As in some situations the import/export of the pool is
>> controlled by any other means, and an accidental pool of the pool may be a
>> destructive action (ie. when the pool maybe from a shared medium like
>> iscsi, and thus should not be mounted by two nodes at the same time).
>>
>>
>> I agree. Should I add another parameter for this? If yes, should this be
>> default to auto-import, or not?
>>
>>
>> Best regards,
>> Adrian Costin
>>
>>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20150213/513a57aa/attachment.htm>