From nobody Sun Jan 19 12:20:48 2025 X-Original-To: virtualization@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 4YbXcc3d7lz5l9qd for ; Sun, 19 Jan 2025 12:20:48 +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 "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YbXcc2njYz3LKJ for ; Sun, 19 Jan 2025 12:20:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1737289248; 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=X4nVL+XwwdWFHJd7jg1AGqh+gp1mA0yDPxLgkmDRIow=; b=rzYXF7wPDtaRuHEkNbQqoOTTpNHWE+xHVEFKIJF/l7kIcV1G6n47mO2XXY7r84ImGUO6+r RL9ncToV1KnjYDJ/JrQfsYcGs80Bdh7fj3hwawa57g/kKwQ2imnVwVm8Wy0WahmseBdCIC I9LcwZ7yk7UEW5HlU5gGyidNYzACIT/ImQDJZ6b4rZMdkqtdIVrXCHAiZXQAYsr+ES+2mp wOORkchFgupAZt5/gvE2seQDiPSJzvUYIVlEeAPhNhaMvq2vlIM8Mqgq2f+Ss10gOHwkI1 emzuj94A0rkPbbLGXxgxF8VQm0UOWp4Zo61QTz9GomyNKLpwj7kGonULL0Wisg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1737289248; 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=X4nVL+XwwdWFHJd7jg1AGqh+gp1mA0yDPxLgkmDRIow=; b=FmECQyPVeLnHcAkOatVPLX3tOqVj9dCoUFVm0+yVsaPoCyQqhBFWoq5FvA/U5G7LN5rU54 dDtdNbZap2TPdrG58i+ORmetayj1M+4NCTJr2JwyWDVS39FXIGxxAH0k56fK+S4zdKF0+G TSv448WdNg0ZBzjQUoe5f3DB4JLv5pVw7qMYiwiU2DZQhdE9sF7e8gT8vPxoMihqp7qF32 MRMbbc2UWqAUvDpXYy9Uyeg9Uh02Dbs1TxRIjVuPlPuau1IyInURHyG9eOCaEXbbRIxpcA yPTSiJhmZwGOoqRiSsk4SwLCaOrJZaRBnQi4HD7WWIoeTJIrDFFWeGDYzjLg9Q== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1737289248; a=rsa-sha256; cv=none; b=pirqTBIpdMCVqWTf2y+32GGBVp2I+buzcno/boWFT3ALvRX0zPHx3YHiEcOivXFdoVg9bx q3lti1OIHjCdoQVTNob0gsiEU7dPfBbbt4vCvZIpZ9r/Mu4OoC5nkvbqxECkKyLCB7XGva YCEhuNID9pV11RrB6ZCIFRHHd1Q+P2ZTdAZ/s97yt/9QVOhnSd/dVCUNXaAEb0g6nr9rSD 51FECwfmTNQzQlEjmR5qAnBjZrppOtNdXi2yiKJfMANsSToNHoTPwb7pUksdi50C3lYEiw TGHMxKTvMXEfdz8fGgr4XaDOvZPkVLvYtp9fXBuE5AXwQnuRqYRwEqwNmMxg0w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YbXcc2Bg5zqN5 for ; Sun, 19 Jan 2025 12:20:48 +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 50JCKmZK057303 for ; Sun, 19 Jan 2025 12:20:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 50JCKm2B057301 for virtualization@FreeBSD.org; Sun, 19 Jan 2025 12:20:48 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: virtualization@FreeBSD.org Subject: [Bug 276522] Setting LUN block size in ctl.conf to 4K causes mismatched block size and crashes in initiators Date: Sun, 19 Jan 2025 12:20:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 13.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: balchen@ste.no X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276522 --- Comment #7 from balchen@ste.no --- (In reply to Alan Somers from comment #4) If you look at #276524, you will see an extensive discussion on this. It se= ems likely that ESXi has misinterpreted the disks, perhaps because of mismatched info in outdated iSCSI pages. I don't know how this would have affected the Windows initiator, but it see= ms it has affected it somehow. If ESXi has never touched the target, Windows s= eems to have no issues with it. If ESXi has touched the target, Windows also fai= ls. Perhaps the incorrect info ESXi derives is stored in MBR/GPT and used by Windows. In either case, it seems there is not much else to do here apart from what = was already done in #276524. --=20 You are receiving this mail because: You are the assignee for the bug.=