[Bug 273772] zpool nested in ZVOL becomes unaccesible when zfsd(8) is running on host
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 14 Sep 2023 08:15:37 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273772
Bug ID: 273772
Summary: zpool nested in ZVOL becomes unaccesible when zfsd(8)
is running on host
Product: Base System
Version: 14.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bhyve
Assignee: virtualization@FreeBSD.org
Reporter: zarychtam@plan-b.pwste.edu.pl
After upgrading to stable/14 a bhyve VM deployed on a ZVOL cannot access its
zpool when zfsd(8) is running on the bhyve host. The VM boots fine when zfsd(8)
on the host machine is shut down. The sysctl knob vfs.zfs.vol.recursive is set
to 0 on the host.
Trying to mount root from zfs:vmzroot/ROOT/default []...
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
Mounting from zfs:vmzroot/ROOT/default failed with error 6; retrying for 3 more
seconds
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
vtbd0: hard error cmd=write 1592-1607
vtbd0: hard error cmd=write 94371896-94371911
vtbd0: hard error cmd=write 94372408-94372423
Mounting from zfs:vmzroot/ROOT/default failed with error 6.
Loader variables:
vfs.root.mountfrom=zfs:vmzroot/ROOT/default
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
--
You are receiving this mail because:
You are the assignee for the bug.