Date: Mon, 22 Jan 2024 20:27:32 +0000 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 Message-ID: <bug-276522-27103-ZEM1wBh7Ju@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-276522-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-276522-27103@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276522 --- Comment #1 from balchen@ste.no --- Having researched some more, I found this from https://manpages.ubuntu.com/manpages/xenial/en/man8/sg_format.8.html -- the documentation for the sg_format command: When this utility is used without options (i.e. it is only given a DEVICE argument) it prints out the existing block size and block count derived from two sources. These two sources are a block descriptor in the response to a MODE SENSE command and the response to a READ CAPACITY command. The reason for this double check is to detect a "format corrupt" state (see NOTES section). This usage will not modify the disk. This describes my scenario perfectly, including the "format corrupt" message which also appears in the ESXi logs. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276522-27103-ZEM1wBh7Ju>