1.0.0-RC1

refactor[gitlab-yml]: Updated gitab ci yaml to trigger the pipeline (…

0.9.0-RC4

feat(seamless_upgrades): make zfs compatible with version 3 and 4 (#2…

0.9.0

feat(seamless_upgrades): make zfs compatible with version 3 and 4 (#2…

0.9.0-RC3

fix(stats, zvol): use dd_uncompressed_bytes instead of dd_used_bytes …

0.9.0-RC2

fix(rebuild_issue): scanner thread exit issue (#223) (#224)

Signed-off-by: Vitta <vitta@mayadata.io>

0.9.0-RC1

fix(rebuild_issue): scanner thread exit issue (#223) (#224)

Signed-off-by: Vitta <vitta@mayadata.io>

0.8.2-RC4

fix(zfs_prop): create zinfo after setting the quorum property (#210) …

0.8.2

fix(zfs_prop): create zinfo after setting the quorum property (#210) …

0.8.2-RC3

feat(zfs): honoring targetip setting during runtime (#212)

to set IP:
zfs set io.openebs:targetip=127.0.0.1:6060 tpool/vol1 (or) zfs set io.openebs:targetip="127.0.0.1:6060" tpool/vol1

to unset IP:
zfs set io.openebs:targetip="" tpool/vol1 (or) zfs set io.openebs:targetip= tpool/vol1

Signed-off-by: Vitta <vitta@mayadata.io>

0.8.2-RC2

fix(zfs): create zinfo after setting the volume properties (#207)

For every volume creation command 'zfs create', zinfo will be created, and, it triggers management connection with target. During handshake in management connection, zrepl sends quorum property.
Quorum property is set after creating zinfo.

If there is race between handshake command and setting quorum property, zrepl may send default quorum property which is 'false' and can cause issues.

This PR is to avoid the race by creating zinfo after setting quorum property.