From nobody Mon Feb 28 09:12:29 2022 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A2BE719EF215 for ; Mon, 28 Feb 2022 09:12:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K6ZQj2f9Qz4pND for ; Mon, 28 Feb 2022 09:12:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 3CA5A18BCF for ; Mon, 28 Feb 2022 09:12:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 21S9CTsP049619 for ; Mon, 28 Feb 2022 09:12:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 21S9CTKo049617 for bugs@FreeBSD.org; Mon, 28 Feb 2022 09:12:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262189] ZFS volume not showing up in /dev/zvol when 1 CPU Date: Mon, 28 Feb 2022 09:12:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: zedupsys@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1646039549; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5BWx3RAOl5glaDmS9wcpaQ5hrGvSc6juwRjfeFKeaxE=; b=MkC47A+mU4PQj6Ve9pc0y2NDowj5VY8Ko9mcJRlK0YUVdpGg+dpueTaDG7gVzHW1K7TVYU MG5OJb2eHB72/hXDaFT5gFs+PGQbawxqP3zUYk5sh81eN8etuv0eFJ4yKqii2o/7No/SiO feyOtPM50CUU6KehRf9ITIypfnxsn7A/V40+Bl1cmWaixW0NPo63WcL5yikOSz1i0nm8Kj eFDo0u81oUujMhbXI89qqu6R/z2yizhnrR02sIbCoMNWwL/TgcSToYvFmWccBONSLe/J45 AqBlsNDO1WURut49h1BVCis82QLIBqEdhl/qRt805IuUTL7slV5VAvO1nqyluQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1646039549; a=rsa-sha256; cv=none; b=se7fT0fFnYM+GBl0zGVJ391O1gn+rzozyj7g2Sk6M0A9uwC30TrWg7dagOd2FS8LKWzduO if8+GRJgCsoGHvAURzCtWxqZsePsM6mQHG3laYfiFmdJdmDqejlIe/BDQY6QGHkvHPVuBP 7Fm640aC6DXG7EO7E+Sg/21DrXkxC66Z8hlOyIbR8YE1m8SVupGWIDio1e7ljO4z5pltRS EhxpqHfWMJYPwhZg4++ODTqa1WQBsLz6+185ql8W/lvCnrpDUGw5SAbUubkYux/iw4sLuW hFDo/obMC4mGHUjFknpStagWY7VJ/CBM/Wqu+JmTeXV8Cnja6xQRe93THsiHCQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262189 --- Comment #9 from Janis --- Now i tried to test the same script with sysctl vfs.zfs.vol.mode=3D2, singl= e CPU, single core. Added sparse option, since it does not reserve space and seems= not to influence the bug. sysctl vfs.zfs.vol.mode=3D2 .. loop .. zfs create -o volmode=3Ddev -s -V 1G $name_pool/data$i .. All ZVOLs show up as would be expected from "zfs create" with vfs.zfs.vol.mode=3D1 as well. The interesting thing is that with sysctl vfs.zfs.vol.mode=3D2 .. loop .. zfs create -o volmode=3Dgeom -s -V 1G $name_pool/dataG$i .. All ZVOLs showed up. I somewhat expected this to fail, since default mode w= as set to DEV, and i thought that create-destroy stuff as mentioned in comment= #2 would mess things up, but no, it did not. But when i switch sysctl value back sysctl vfs.zfs.vol.mode=3D1 .. loop .. zfs create -o volmode=3Ddev -s -V 1G $name_pool/dataD$i .. No ZVOL shows up in /dev/zvol Based on this, it seems that actually it would be better if default value is DEV, since then in both "zfs create" calls, ZVOLs show up (bug does not manifest itself). So to trick away this bug, it could be possible to set vfs.zfs.vol.mode=3D2(DEV) as default and for "zfs create" command to auto-f= ill volmode=3Dgeom if volmode is not specified. I would not like this to be a solution, since that does not fix the bug, it just masks it, which might manifest itself in different cases anyways. It seems that value change vfs.zfs.vol.mode=3D2 might help in some systems = to minimize problems with ZVOLs whose type is DEV. So it seems that second part of comment #2 might be closer where the bug co= mes from. What i did not get though is, why then with vfs.zfs.vol.mode=3D2; zfs create volmode=3Dgeom did not fail? Does it take different path then not the create-destroy-create? --=20 You are receiving this mail because: You are the assignee for the bug.=