Hello Darren,
Thursday, September 14, 2006, 5:42:20 PM, you wrote:
>> > If you *never* want to import a pool automatically on reboot you just have
>> > to delete the
>> > /etc/zfs/zpool.cache file before the zfs module is being loaded.
>> > This could be integrated into SMF.
>>
>> Or you could
> > If you *never* want to import a pool automatically on reboot you just have
> > to delete the
> > /etc/zfs/zpool.cache file before the zfs module is being loaded.
> > This could be integrated into SMF.
>
> Or you could always use import -R / create -R for your pool management. Of
> course, t
> If you *never* want to import a pool automatically on reboot you just have to
> delete the
> /etc/zfs/zpool.cache file before the zfs module is being loaded.
> This could be integrated into SMF.
Or you could always use import -R / create -R for your pool management. Of
course, there's no way
> The OP was just showing a test case. On a real system your HA software
> would exchange a heartbeat and not do a double import. The problem with
> zfs is that after the original system fails and the second system imports
> the pool, the original system also tries to import on [re]boot, and the