Note that it is expected that the cluster will force
import, so in a
i was talking about creation, not import.
You must be running an older version of Solaris. The
s10u4 + sc 3.2
Anyway, bug has now been accepted.
With cluster and SAN, zfs does _yet_ not behave normally :)
Thanks for your
When moving pools, we use of course export/import or sczbt suncluster stuff.
Nevertheless, we dont want to use zfs as global FS with concurrent access, just
use it like svm or vxvm to declare volumes usable by cluster's nodes (and
used by only once at a time).
so, it seems to me a bit
Christophe Rolland wrote:
When moving pools, we use of course export/import or sczbt suncluster stuff.
Nevertheless, we dont want to use zfs as global FS with concurrent access,
just use it like svm or vxvm to declare volumes usable by cluster's nodes
(and used by only once at a time).
so,
This is probably because ZFS is not supported as a global filesystem. If you
move the
zpool between cluster nodes, you'll need to zpool export it on the first node,
and
zpool import it on the second node.
-Tim
This message posted from opensolaris.org
Hi
I got a san disk visible on two nodes (global or zone).
On the first node, i can create a pool using zpool create x1 sandisk.
If i try to reuse this disk on the first node, i got a vdev in use warning.
If i try to create a pool on the second node using the same disk, zpool create
x2 sandisk,
