[Bug 234576] hastd exits ungracefully

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234576

            Bug ID: 234576
           Summary: hastd exits ungracefully
           Product: Base System
           Version: 12.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: bugs at FreeBSD.org
          Reporter: rasmus at gal.dk

OS: FreeBSD 12.0-RELEASE

I want to have a poor mans HAST + bhyve solution, running OS and hastd-device
on the same physical disk on each server. However hastd dies and produces the
following in messages:

Jan  2 16:11:13 vip02 ZFS[9633]: vdev state changed,
pool_guid=$12664153310291685811 vdev_guid=$13719543425671811341
Jan  2 16:11:13 vip02 ZFS[9634]: vdev is removed,
pool_guid=$12664153310291685811 vdev_guid=$13719543425671811341
Jan  2 16:11:18 vip02 hastd[9563]: [test] (primary) Worker process exited
ungracefully (pid=9588, exitcode=71).

If I use the partition (ada0p4) directly, without using HAST, I am able to
install FreeBSD as a guest just fine. 

How to reproduce:

- Configure bhyve

https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html

21.7.1 followed to the dot.

- Configure hastd

https://www.freebsd.org/doc/handbook/disks-hast.html

17.14.2 followed to the dot. 

# cat /etc/hast.conf
resource test {
        on vip01 {
                local /dev/ada0p4
                remote 192.168.212.202
        }
        on vip02 {
                local /dev/ada0p4
                remote 192.168.212.201
        }
}
#

- Setup ZFS pool and create volume for guest

# zpool create ztest /dev/hast/test
# zfs create -o volmode=dev ztest/fbsdguestdisk0

- Start installing FreeBSD in the guest

# sh /usr/share/examples/bhyve/vmrun.sh -c 1 -m 1024M -t tap0 -d
/dev/zvol/ztest/fbsdguestdisk0 -i -I FreeBSD-12.0-RELEASE-amd64-disc1.iso
fbsdguest


- Start to install - all default. The disk can be seen just fine, but then
choosing either ZFS or UFS on the disk, will result in hastd quits
ungracefully.

In the guest it spews out:

***
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
            to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
kern.geom.part.mbr.enforce_chs: 0 -> 0
***

and then stalls (of course, since the device vanished).

According to the documentation:

https://www.freebsd.org/doc/handbook/disks-hast.html

"There is no difference between using HAST-provided devices and raw disks or
partitions."

But that seems not to be the case - since it works fine if I skip HAST and
configures the zpool directly on ada0p4 on one of the servers.

Is it because I am using HAST on a partition?

-- 
You are receiving this mail because:
You are the assignee for the bug.