All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: target-devel@vger.kernel.org
Subject: Re: MaxTransferLength
Date: Tue, 24 Apr 2018 12:38:12 +0000	[thread overview]
Message-ID: <1c3a6c87-9afa-3f7c-2c76-24df8f021290@suse.de> (raw)
In-Reply-To: <20180424122512.GQ27687@hydro.skol.ch>

On 04/24/2018 02:25 PM, Nicolas D wrote:
> 
> Hello everyone,
> 
> I tried googling a lot about this problem, but I had no luck till now.
> 
> I am having some trouble to read from a dvd/bd drive that is configured
> with targetcli with pscsi driver on different not so old linux versions:
>   - debian (version: saddly don't have the computer with me and don't
>     remember exactly but should be Jessie)
>   - ubuntu (14.04/kernel 3.13)
> 
> The problem is the same with all the initiator/os I could play with:
> 
> - Core-iSCSI/Linux
> - MS-initiator/Windows
> - StarWind/Windows
> - Sns GlobalSan/MacOS
> 
> The actual problem is that my target don't react well when the initiator
> ask to read more than 16KB in one read instruction: the response is a
> sense error or unit error (error discovered in pcap trace, thanks to
> wireshark).
> 
> I could lower the MaxTransferLength with the "MS-initiator/Windows" and
> for that initiator/os it works now perfectly.
> 
> https://support.zadarastorage.com/hc/en-us/articles/213024226-Recommended-Windows-iSCSI-initiator-Registry-configuration
> 
> But Sns GlobalSan for example does not support limiting read size on is
> side, and I think it's definitively the target that has to tell the
> initiator about this MaxTransferLength attribute, or I may be wrong?
> 
> I tried to tweak some parameters with targetcli, but:
> - lowering fabric_max_sectors does not seem to help
> - hw_max_sectors%6 hw_block_size 48 are read-only
> 
> I have definitively trouble finding documentation on all other
> backend attributes.
> 
> I have the impression that my problem is more config related, it's why I
> did not took the time to write all exact versions of the os/tools I use.
> 
> If you think I am wrong, I'll provide all useful informations.
> 
> Thank you for your help and for all the job already made to have this
> iscsi stack working in linux.
> 

'pscsi' is the SCSI pass-through, so it'll be presenting the values from 
the underlying device; I doubt you can change that.

What you could try is to mount the DVD, and export the mountpoint via 
the file backend; that way you should be able to tweak the parameters.

Cheers,

Hannes

  reply	other threads:[~2018-04-24 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 12:25 MaxTransferLength Nicolas D
2018-04-24 12:38 ` Hannes Reinecke [this message]
2018-04-24 12:53 ` MaxTransferLength Bryant G. Ly
2018-04-25 10:13 ` MaxTransferLength Nicolas D
2018-04-25 13:46 ` MaxTransferLength Bryant G. Ly
2018-05-23 20:48 ` MaxTransferLength Nicolas D
2018-05-24 13:46 ` MaxTransferLength Bryant G. Ly
2018-06-13 11:31 ` MaxTransferLength Nicolas D

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=1c3a6c87-9afa-3f7c-2c76-24df8f021290@suse.de \
    --to=hare@suse.de \
    --cc=target-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.