Re: sysfs interface sometimes does not get the block device name, for a logged in iSCSI target

wrote: > > On Monday, December 17, 2018 at 9:08:54 AM UTC-8, Satyajit Deshmukh wrote: >> >> >> >> On Sunday, December 16, 2018 at 5:30:29 PM UTC-8, The Lee-Man wrote: >>> >>> On Friday, December 14, 2018 at 12:13:46 PM UTC-8, Satyajit Deshmukh >>&g

Re: sysfs interface sometimes does not get the block device name, for a logged in iSCSI target

On Sunday, December 16, 2018 at 5:30:29 PM UTC-8, The Lee-Man wrote: > > On Friday, December 14, 2018 at 12:13:46 PM UTC-8, Satyajit Deshmukh wrote: >> >> Hello, >> >> An update on the issue. I could observe that the target entries were not >> populated unde

Re: sysfs interface sometimes does not get the block device name, for a logged in iSCSI target

to enable some debugging, to debug this? On Monday, December 10, 2018 at 5:52:19 PM UTC-8, Satyajit Deshmukh wrote: > > Hello, > > We are fairly frequently now running into this. Looks like an issue with > the sysfs interface. > > iscsi_sysfs_get_blockdev_from_lun() someti

sysfs interface sometimes does not get the block device name, for a logged in iSCSI target

Hello, We are fairly frequently now running into this. Looks like an issue with the sysfs interface. iscsi_sysfs_get_blockdev_from_lun() sometimes does not find the SCSI block device (say /dev/sdd) for a logged in iSCSI target. Thus, iscsiadm -m session -P0 does not print the SCSI device block

Re: Patch for faster iscsi logins by optimized idbm_lock() and idbm_unlock() APIs

Thanks Lee for code review comments! Looking at code from lock stacking perspective, and would get back shortly. Through some more testing, we believe there's another major issue with the way the locking is done today, that caused a deadlock on our setup. Existing iscsiadm code creates a symboli

Patch for faster iscsi logins by optimized idbm_lock() and idbm_unlock() APIs

Hello, We had a use case, where we had to log into multiple iSCSI targets in parallel. And it was important for these operations to complete in a timely manner. We found 2 major codes that caused large delays in the login command: 1. idbm_lock() and idbm_unlock() APIs 2. session_is_running() dup

Re: iscsiadm utility to update persistent address of all sessions, to a given address.

SNS asynchronous notification system. Thanks, Satyajit On Thu, May 31, 2018 at 2:59 PM, The Lee-Man wrote: > On Wednesday, February 8, 2017 at 1:56:07 AM UTC-8, Satyajit Deshmukh > wrote: >> >> Hello, >> >> We have a setup, where we are using the iSCSI redirect functi

Re: iscsiadm utility to update persistent address of all sessions, to a given address.

Adding Chris Leech to see if this could be used by the iSCSI community. Thanks, Satyajit On Wed, Feb 8, 2017 at 1:56 AM, Satyajit Deshmukh < satyajit.s.deshm...@gmail.com> wrote: > Hello, > > We have a setup, where we are using the iSCSI redirect functionality, > where we c

iscsiadm utility to update persistent address of all sessions, to a given address.

com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout. commit dcee6c1e4b9f98472f814a69632a42a98bb71559 Author: Satyajit Deshmukh Date: Wed Feb 8 01:19:06 2017 -0800 iscsiadm utility to update persistent address of all sessions, to a given address. Usag