From: "Björn Wiggert (wiggert.it)" <b@wiggert.it>
To: "stgt@vger.kernel.org" <stgt@vger.kernel.org>
Subject: LinuxIO (LIO) target @ Debian 10 and VMware 6.7 Initiator: Detected WRITE_PROTECTED LUN Access for 0x00000000
Date: Mon, 28 Dec 2020 18:43:19 +0100 [thread overview]
Message-ID: <zarafa.5fea1937.73b4.3947be6e1a89f482@lx18.cmks.de> (raw)
Hi, we are running
* QNAP NAS
* Debian 10
* Host VMware 6.7U3 Hypervisor
a) Exporting an iSCSI-LUN-target with the QNAP, what is using LIO therfor, and accessing it from VMware (read/write) works fine.
b) Exporting an iSCSI-LUN-target with a fresh Debian 10 using LIO and accessing it with a Windows 7 iSCSI initiator (read/write) works fine.
Using the target b) (Debian 10 / LIO) and the initiator a) (VMware v6.7) works as far as
* VMware sees the target host
* VMware can login and sees the target
* VMware can READ the data on the LUN (sees partition table, size of it, partition types, etc)
As soon as we try to write anything VMware reports
> 2020-12-28T14:36:00.775Z info hostd[2098690] [Originator@6876 sub=Partitionsvc opID=esxui-2f96-fbd9 user=root] Status : 255 Output: gpt 0 0 0 0
>
> Error : Error: Read-only file system during write on /dev/disks/naa.60014054b666e78a1c443ee941c60e3e SetPtableGpt: Unable to commit to disk
and the Debian 10 box reports:
> kernel: [ 80.210044] TARGET_CORE[iSCSI]: Detected WRITE_PROTECTED LUN Access for 0x00000000
I don't recognize why VMware mounts the iSCSI LUN read-only but Windows 7 mounts it read-write and VMware mount the QNAP-iSCSI-LUN also read-write.
I appreciate any hint - thank you therfor in advance.
Jan
Â
next reply other threads:[~2020-12-28 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 17:43 Björn Wiggert (wiggert.it) [this message]
2020-12-30 3:09 ` LinuxIO (LIO) target @ Debian 10 and VMware 6.7 Initiator: Detected WRITE_PROTECTED LUN Access for 0x00000000 Mark Harvey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=zarafa.5fea1937.73b4.3947be6e1a89f482@lx18.cmks.de \
--to=b@wiggert.it \
--cc=stgt@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).