Date: Fri, 25 Feb 2022 13:27:06 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 251828] "zfs create -o <mode>" ignores mode when creating the device node Message-ID: <bug-251828-3630-WI8e9PeNxx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251828-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-251828-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251828 Janis <zedupsys@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zedupsys@gmail.com --- Comment #5 from Janis <zedupsys@gmail.com> --- I tested this bug, whose fix seems to have introduced bug #262189 as report= ed by me. In 13.0-RELEASE there was no way to reproduce this bug. In each shown case received answer from gpart was: gpart: arg0 'zvol/testpool/vol': Invalid argument So i specially tested 12.2-RELEASE, but i could not repeat it exactly, but partially. I believe that it is due to the reasoning as in bug #262189, sin= ce i had virtual machine, VirtualBox, 1 vCPU assigned. Thus, in each case i got = the same answer, volmode=3Ddev was not respected at all. # zfs create -o volmode=3Ddev -V 64m testpool/vol # gpart create -s gpt /dev/zvol/testpool/vol zvol/testpool/vol created # zfs create -V 64m testpool/vol # zfs set volmode=3Ddev testpool/vol # gpart create -s gpt /dev/zvol/testpool/vol zvol/testpool/vol created But if i did this flow: # zfs create -V 64m testpool/vol # zfs set volmode=3Ddev testpool/vol # .. reboot system .. # gpart create -s gpt /dev/zvol/testpool/vol gpart: arg0 'zvol/testpool/vol': Invalid argument then returned value is as expected. In 12.2-RELEASE i could not reproduce bug #262189 --=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-3630-WI8e9PeNxx>