Date: Sun, 13 Dec 2020 23:29:17 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 251828] "zfs create -o <mode>" ignores mode when creating the device node Message-ID: <bug-251828-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251828 Bug ID: 251828 Summary: "zfs create -o <mode>" ignores mode when creating the device node Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: asomers@FreeBSD.org zvols have a "volmode" property that controls how their device nodes are created: as geom devices (default), as non-geom character devices, or not at all. At least, it's supposed to do that. But on 13-CURRENT, the volmode property gets ignored at creation time. The device always gets created as = the default type instead. The easiest way to demonstrate the problem is to use gpart on the device no= de.=20 It isn't supposed to work if the node is a non-geom device. But it does! # zfs create -o volmode=3Ddev -V 64m testpool/vol # gpart create -s gpt /dev/zvol/testpool/vol zvol/testpool/vol created However, if we change the volmode property after creation, then ZFS destroys and recreates the device node with the correct volmode. # zfs create -V 64m testpool/vol # zfs set volmode=3Ddev testpool/vol # gpart create -s gpt /dev/zvol/testpool/vol gpart: arg0 'zvol/testpool/vol': Invalid argument --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251828-227>