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

Pablo Ruiz pablo.ruiz at gmail.com
Fri Feb 13 13:51:37 CET 2015


Hi Wolfgang,

I think you are confusing (probably due to my really short description of
the issue at the original email [my fault]) using an iscsi storage entry at
storage.cfg with using iscsi to mount the block device where a local zfs
pool is stored. In our case, we have a couple of those, and we mount them
only at one node of the cluster at a time.

Yes, there maybe more ways to accomplish the same thing (ie. avoiding an
accidental import of a pool by proxmox), but most of them relay on
scripting and event handling which seems more risky (think on script
failures, race conditions, etc.) than having a clear override option at
storage.cfg.

Just my two cents.



On Fri, Feb 13, 2015 at 7:10 AM, Wolfgang <wolfgang at linksystems.org> wrote:

> 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/0c566172/attachment.htm>


More information about the pve-devel mailing list