From: Gionatan Danti <g.danti@assyoma.it>
To: target-devel@vger.kernel.org
Subject: Re: Limit logins or connections to the same target LUN
Date: Mon, 25 Mar 2019 18:33:38 +0000 [thread overview]
Message-ID: <b83a29800bb1c3fd2969f173e9dc70ff@assyoma.it> (raw)
In-Reply-To: <17b94268-631e-515b-ccb3-f1b6ffcdd797@assyoma.it>
Il 04-03-2019 18:25 Gionatan Danti ha scritto:
> Il 28-02-2019 16:19 Gionatan Danti ha scritto:
>> Hi all,
>> I would like to understand if, and how to, limit the maximum number of
>> simultaneous connections (or logins) to a specific LUN (similar in how
>> the "MaxSession" option worked in the old ietd).
>>
>> I am exporting a LUN with a general purpose filesystem (non cluster
>> aware) and I would be 100% sure that only a single machine at a time
>> can mount it.
>>
>> At the moment, I protected the iSCSI LUN with both an IP-based access
>> list and a username/password combo, but hard limiting the maximum
>> number of connections opened against it to 1 (one) would be a nice
>> thing...
>>
>> Also, I am aware of SCSI persistent reservations (sg_persist) but,
>> while working well, they are somewhat harder to setup.
>>
>> Thank you,
>> regards.
>
> Hi all,
> any suggestions?
>
> Thanks.
Sorry to ask again... does someone know the answer to my question? Am I
posting on the wrong list?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2019-03-25 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 15:19 Limit logins or connections to the same target LUN Gionatan Danti
2019-03-04 17:25 ` Gionatan Danti
2019-03-25 18:33 ` Gionatan Danti [this message]
2019-03-25 19:13 ` Bart Van Assche
2019-03-27 15:28 ` Gionatan Danti
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=b83a29800bb1c3fd2969f173e9dc70ff@assyoma.it \
--to=g.danti@assyoma.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox