Zfs backend storage for lxd cluster

LXD
,
1

I have question

I use zfs as backend storage for lxd cluster, but when joining cluster there is a difference in “zpool status” on node1 and node2.

On node1 like this:

  pool: apps_pool
 state: ONLINE
  scan: scrub repaired 0B in 0 days 01:35:51 with 0 errors on Sun Jun 12 08:59:53 2022
config:

        NAME        STATE     READ WRITE CKSUM
        apps_pool   ONLINE       0     0     0
          raidz2-0  ONLINE       0     0     0
            sdd     ONLINE       0     0     0
            sde     ONLINE       0     0     0
            sdf     ONLINE       0     0     0
            sdg     ONLINE       0     0     0
            sdh     ONLINE       0     0     0
            sdi     ONLINE       0     0     0

On node2 like this:

  pool: apps_pool
 state: ONLINE
  scan: none requested
config:

        NAME                                            STATE     READ WRITE CKSUM
        apps_pool                                       ONLINE       0     0     0
          /var/snap/lxd/common/lxd/disks/apps_pool.img  ONLINE       0     0     0

When node2 joins the cluster, the zfs backend storage becomes an image:

/var/snap/lxd/common/lxd/disks/apps_pool.img

Can the zfs backend storage on node2 not be an image and be the same as node1 ?

Thanks

2

Yes when creating the storage pool on the cluster, you have to specify the source property for each cluster member, e.g.

lxc storage create myzfs zfs source=... --target=member1
lxc storage create myzfs zfs source=... --target=member2
lxc storage create myzfs zfs source=... --target=member3
lxc storage create myzfs zfs # Finalise creation
3

Can the source “/var/snap/lxd/common/lxd/disks/apps_pool.img” be changed to the zpool I created like node1 ?

Because when “lxd init” on node2 to join the cluster there is an error because the zpool already exists.