Closed heinrichrebehn closed 8 years ago
Heinrich,
There have been a few changes to the way this is handled (well, other changes that affect this). Please try the newest .dmg under releases and let me know if you are still experiencing this problem.
Hi, I also have this problem to. I installed from sources. And also I examined the source code. I didn't find any problem. You saved active target list, unmount and logout while sleeping. And when computer wake up login to the saved targets.
While I looked at logs, I found that:
07/07/16 12:31:39.175 PM iscsid[75721]: login to
And also an interesting log:
07/07/16 12:35:11.597 PM iscsid[75721]: discovery is taking longer than the specified discovery interval. Consider increasing discovery interval
I started tcpdump at at both side, I do not find any network problem. Also SendTargets=All command took in milliseconds.
If I killed iscsid (respawns by kernel), Login and mounting disk is performed without any error.
However second log (about discovery interval) continues.
My interval is 60 seconds.
@kazimsarikaya Does this happen when the computer sleeps on its own, or if you put it to sleep (using the apple menu on the top left)?
Are you using WiFi or a wired connection? Does this occur for both connection types?
@nsinenian I am only using wired 1gbit connection. both if auto sleep and putting to sleep causes this. the problem is happened after wake up. sleeping unmounts and logouts disk. however after wake up it gets timeouts to login.
I found an interesting error too. If I restart my computer, this timeout error increases boot time (also for login i need to kill iscsid again.)
I think it is a kind of order service run order problem. Iscsid runs and tries before network is up, not only link (layer 1) especially routing/ip address etc (layer 3).
I looked at launchd documantation.
If your daemon depends on the network being available, this cannot be handled with dependencies because network interfaces can come and go at any time in OS X. To solve this problem, you should use the network reachability functionality or the dynamic store functionality in the System Configuration framework. This is documented in System Configuration Programming Guidelines and System Configuration Framework Reference. For more information about network reachability, see Determining Reachability and Getting Connected in System Configuration Programming Guidelines.
@kazimsarikaya "I found an interesting error too. If I restart my computer, this timeout error increases boot time (also for login i need to kill iscsid again.)"
This is strange - after a restart the previous state (previous error) should not matter. Do you have auto-login enabled by any chance? That would explain things; if auto-login was enabled and the network was not available it might take longer...
"I think it is a kind of order service run order problem. Iscsid runs and tries before network is up, not only link (layer 1) especially routing/ip address etc (layer 3)."
I agree, I think this is what is happening as well.
I think that the network reachability API may solve some of these problems. I haven't experienced any of these issues on my machine and you guys are the first to report it, so will look into this and address it for the next release. Please keep in mind that the daemon does not attempt to keep alive any sessions (e.g., if network drops out, the session is gracefully dropped, and you'd have to login again). This may be something to implement in the near future. As for sleep, I assumed that the network would come up upon sleep within the timeout time of the connection (several seconds). This has always worked on my machine but is not a good assumption.
@nsinenian yes i am using auto-login enabled. hence it always retry to mount disk which is my wish. Bu when network is not ready there is a big problem. in my environment my san/nas is in different network with dynamic routing. I can not use NFS every where because i need raw disks. hence i use iscsi. i do not like fc and this is not topic of this issue.
you do not need to use reachability api, you are trying only once, retry auto-login in a loop with incremented sleeps like wait 10 seconds, 30 seconds, 60 seconds, 120 seconds and go on.
I tried to implement, however, i didn't find flow chart of the functions and where i should edit.
@kazimsarikaya auto-login does not "always retry to mount ...". Instead, as you say later, auto-login only logs into the target one time when the daemon starts. This is not a mistake or accident, but rather done by design. The feature you're thinking of is typically called a "persistent" target or connection in other iSCSI initiators, which maintains a connection in the event of network drops. This is not yet implemented in this initiator.
I believe that your observations regarding boot-up taking longer are related to the sleep mode issue. It seems to me that in both cases, the daemon tries to login before the network is up. In one case it is during boot, in the other case it is after recovering from sleep.
There is an efficient and appropriate way of solving all of these issues at once - both the boot-time issue and the sleep-mode issue. Polling is generally frowned upon as it blocks access to the daemon.
I'll put something together for you to test soon...
Yes boot-up an sleep is causes same issue. Persistence feature is what i wanna. sorry for my mistake for auto-login. every time network returns, i call the login, hence i think auto login what i wanna.
i am waiting good news from you about persistence.
best regards
@kazimsarikaya Please try the latest commit on the features/network-availability branch. There is a "persistent" option in the target configuration that is enabled by default (iscsictl list target-config ... can be used to view this). It will cause the daemon to catch dropped connections and queue logins to those targets once they are accessible again. This should also address the sleep problem - if the machine wakes up it will queue the re-login operation until the network interfaces are back up.
Please let me know how it works out!
If I checkout new branch: git checkout features/network-availability
After compile: The first fatal error:
/Users/kazim/Documents/Xcode Projects/iSCSIInitiator/Source/User/iSCSI Framework/iSCSIIORegistry.c:41:10: fatal error: 'iSCSIHBATypes.h' file not found
^
1 error generated.
Sorry about that - I hadn't committed the project file; it is now committed and I'm able to download and build using ./build under Scripts. Please try again.
@nsinenian Now i can build. However there is a bug that i can not modify initiator-config.
kazimmacev:Scripts kazim$ sudo iscsictl modify initiator-config -node-alias kazimmacev
Initiator settings have been updated
kazimmacev:Scripts kazim$ iscsictl list initiator-config
iqn.2015-01.com.localhost:initiator
node-alias localhost
Authentication: none
CHAP-name localhost
CHAP-secret
Also everything I write runs successfully:
kazimmacev:Scripts kazim$ sudo iscsictl modify initiator-config -i-am-bad settings Initiator settings have been updated
Probably it is about new initiator setting. There is a parsing error.
Other commands works as expected. May be daemon can not save new settings. Persistent option?
The persistence is exactly what I'm after also. However, the change mentioned above doesn't seem to work?
Firstly, the target is logged in and working fine.
iscsictl list targets iqn.2017-07.com.lisa:tgt2 <active, static, sid 0, tpgt 1, ösid 0x900> 10.0.0.101 <active, cid 0, port 3260, interface default>
Then goto sleep via sleep option in apple menu, wake up, reestablish network and the target shows and remains inactive.
auto-login and persistent however are both enabled.
iscsictl list target-config iqn.2017-07.com.lisa:tgt2
iqn.2017-07.com.lisa:tgt2 <active, static, sid 0, tpgt 1, tsid 0x900>
node-alias:
auto-login: enabled
persistent: yes
Configuration:
MaxConnections 1 (1)
ErrorRecoveryLevel 0 (0)
HeaderDigest (none)
DataDigest (none)
Authentication: none
CHAP-name
CHAP-secret
Using the network availability branch.
@kazimsarikaya FYI, you do not need to use sudo anymore (see Authorization in wiki for how to restrict access to settings), but this is not the problem. I am unable to reproduce your "modify initiator-config" problem (it works fine on my machine). I am confused as to what the problem might be. The persistent option is enabled in target-config, not initiator-config. FYI, there is in fact a "bug" where if you enter junk it will just ignore it and say "Initiator settings updated" (I just have not implemented additional input validation yet and friendly messages; this is a small item on the to-do list). So, are you telling me that the daemon does not reconnect to the target after a wake-up event?
@lulunzb What is your OS X version? Are you on a wired or wireless connection when connecting to the target? Can you please look at the system logs before going to sleep and after wakeup and tell me if anything is posted after wakeup? You'd need to look in the console under "system.log" (under the files section). I am unable to reproduce this on my machine so I need your help troubleshooting.
El Capitan 10.11.5 Wireless connection
I'll have to reinstall and get the log info, will do so shortly.
I could only get the target going again by explicitly logging in.
Here is the system log for a restart... you'll not that it fails to login as the network is not yet available and I cannot see it retry. Most relevant time stamps.
18.05.43 - reboot initiated. 18.06:29 - iscsi login failed 18:06:56 - en0 up.
Hope it helps.
Jul 24 18:05:43 Mac-Air shutdown[836]: reboot by Owner: Jul 24 18:05:43 Mac-Air kernel[0]: Process launchd [1] disabling system-wide I/O Throttling Jul 24 18:05:43 Mac-Air kernel[0]: Process launchd [1] disabling system-wide CPU Throttling Jul 24 18:05:43 Mac-Air shutdown[836]: SHUTDOWN_TIME: 1469349343 389622 Jul 24 18:05:43 Mac-Air com.apple.xpc.launchd1: System shutdown initiated by: shutdown.836<-sessionlogoutd.834<-launchd.1 Jul 24 18:06:25 localhost bootlog[0]: BOOT_TIME 1469349385 0
Jul 24 18:06:28 --- last message repeated 1 time ---
Jul 24 18:06:27 localhost kernel[0]: Longterm timer threshold: 1000 ms
Jul 24 18:06:27 localhost kernel[0]: PMAP: PCID enabled
Jul 24 18:06:27 localhost kernel[0]: PMAP: Supervisor Mode Execute Protection enabled
Jul 24 18:06:27 localhost kernel[0]: Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64
Jul 24 18:06:27 localhost kernel[0]: vm_page_bootstrap: 836537 free pages and 203847 wired pages
Jul 24 18:06:27 localhost kernel[0]: kext submap [0x
Jul 24 18:06:27 localhost kernel[0]: initting Scan Manager controller 0x9ab3c8db7e74d337 ioservice 0x9ab3c8db1f89cc37 interface 0x9ab3c8db1fa81b37 ioservce 0x9ab3c8db7e74d337
Jul 24 18:06:27 localhost kernel[0]: bpfAttach len 64 dlt 12
Jul 24 18:06:27 localhost kernel[0]: fInterfaceSnapshots is missing
Jul 24 18:06:28 --- last message repeated 9 times ---
Jul 24 18:06:27 localhost kernel[0]: Waiting for DSMOS...
Jul 24 18:06:28 localhost digest-service[141]: label: default
Jul 24 18:06:28 localhost digest-service[141]: dbname: od:/Local/Default
Jul 24 18:06:28 localhost digest-service[141]: mkey_file: /var/db/krb5kdc/m-key
Jul 24 18:06:28 localhost digest-service[141]: acl_file: /var/db/krb5kdc/kadmind.acl
Jul 24 18:06:28 localhost digest-service[141]: digest-request: uid=0
Jul 24 18:06:28 localhost kdc[94]: krb5_kdc_set_dbinfo: failed to create root node: /Local/Default
Jul 24 18:06:28 localhost com.apple.xpc.launchd1: Service exited with abnormal code: 1
Jul 24 18:06:28 localhost com.apple.xpc.launchd1: Service only ran for 1 seconds. Pushing respawn out by 9 seconds.
Jul 24 18:06:28 localhost com.apple.xpc.launchd1: Service "com.apple.ManagedClient.startup" tried to hijack endpoint "com.apple.ManagedClient.agent" from owner: com.apple.ManagedClient
Jul 24 18:06:28 localhost com.apple.SecurityServer[85]: Entering service
Jul 24 18:06:28 localhost distnoted[111]: # distnote server daemon absolute time: 5.091843166 civil time: Sun Jul 24 18:06:28 2016 pid: 111 uid: 241 root: yes
Jul 24 18:06:28 localhost AirPlayXPCHelper[104]: 2016-07-24 06:06:28.260533 PM [AirPlayEndpointManagerMeta] metaManager_createAirPlayEndpointManager Using NAPS Endpoint Manager
Jul 24 18:06:28 localhost AirPlayXPCHelper[104]: 2016-07-24 06:06:28.281779 PM [WiFiManagerCore] ### Bind to fallback "awdl0" failed: -3900/0xFFFFF0C4 kA11ParamErr
Jul 24 18:06:28 localhost AirPlayXPCHelper[104]: 2016-07-24 06:06:28.282445 PM [APTransportTrafficRegistrar] APTransportTrafficRegistrar: Deregister AirPlay traffic for AWDL at MAC 00:00:00:00:00:00 with target infra non critical PeerIndication=0 err=-3900
Jul 24 18:06:28 localhost AirPlayXPCHelper[104]: 2016-07-24 06:06:28.282821 PM [AirPlay] trafficRegistrar_resetRegistrationInternal signalled -3900/0xFFFFF0C4 kA11ParamErr: APTransportTrafficRegistrar: reset registration failed
Jul 24 18:06:28 localhost hidd[103]: __IOHIDSessionScheduleAsync_block_invoke: thread_id=0x700000081000
Jul 24 18:06:28 localhost hidd[103]: HID Session async scheduling initiated.
Jul 24 18:06:28 localhost hidd[103]: HID Session async root queue running at priority 63 and schedule 2.
Jul 24 18:06:28 localhost ifcstart[67]: CFPasteboardRef CFPasteboardCreate(CFAllocatorRef, CFStringRef) : failed to create global data
Jul 24 18:06:28 --- last message repeated 7 times ---
Jul 24 18:06:28 localhost hidd[103]: HID Session async scheduling complete.
Jul 24 18:06:28 localhost hidd[103]: Successfully opened the IOHIDSession
Jul 24 18:06:28 localhost digest-service[141]: digest-request: netr probe 0
Jul 24 18:06:28 localhost digest-service[141]: digest-request: init request
Jul 24 18:06:28 localhost blued[90]: Delete logs
Jul 24 18:06:28 localhost digest-service[141]: digest-request: init return domain: BUILTIN server: LOCALHOST indomain was:
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: KScsiPrt::probe
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: [IOBluetoothFamily][staticBluetoothTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0xa800
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: [IOBluetoothFamily][start] -- completed
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: [IOBluetoothHostController][start] -- completed
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: KScsiPrt::start
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: LoadPortals All
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: succesfuly open file 9488 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: ReadFile 0 4 0 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: ReadFile 256 256 0 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: ReadFile 1024 256 0 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: ReadFile 1280 256 0 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: ReadFile 1536 256 0 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: ReadFile 4096 4 0 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: ReadFile 8192 1296 0 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: KernSafeSCSIEmulatorIOKitDriver mountDevice
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: KernSafeSCSIEmulator::initSocket created 3146eae8
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Socket connect error 33 6500000a 48140 Jul 24 18:06:29 Mac-MacBook-Air blued[90]: INIT -- Host controller is published Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Problem connecting to the network.
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: iscsi login 51 6500000a 3260 iqn.2017-07.com.lisa:tgt2.
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Waiting for thread exit.
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Threadid exit
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Error to logon to iSCSI disk c0000008.
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: initializedCreate emulator failed e0000001
………………………
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: [IOBluetoothHostController::setConfigState] calling registerService Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: \ [IOBluetoothFamily][ProcessBluetoothTransportShowsUpActionWL] -- calling IOBluetoothFamily's registerService() -- 0xcf40 -- 0x6800 -- 0xa800 ** Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: \ [IOBluetoothFamily][ProcessBluetoothTransportShowsUpActionWL] -- Connected to the transport successfully -- 0xcf40 -- 0x6800 -- 0xa800 ** Jul 24 18:06:29 Mac-MacBook-Air blued[90]: [BluetoothHIDDeviceController] EventServiceConnectedCallback Jul 24 18:06:29 Mac-MacBook-Air blued[90]: [BluetoothHIDDeviceController] EventServiceDisconnectedCallback Jul 24 18:06:29 Mac-MacBook-Air blued[90]: [BluetoothHIDDeviceController] EventServiceConnectedCallback Jul 24 18:06:29 Mac-MacBook-Air blued[90]: [BluetoothHIDDeviceController] EventServiceDisconnectedCallback Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: PPGTT is enabled Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Previous shutdown cause: 3 Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: DSMOS has arrived Jul 24 18:06:29 Mac-MacBook-Air loginwindow[99]: Login Window Application Started Jul 24 18:06:29 Mac-MacBook-Air com.apple.xpc.launchd1: The JoinExistingSession key is only available to Application services. Jul 24 18:06:29 Mac-MacBook-Air networkd[176]: -[NETInterfaceManager updateInterfaces] nwi_state_copy() returned NULL Jul 24 18:06:29 Mac-MacBook-Air mds[65]: (ImportServer.Normal:1808) UseBulkImporter 0 ForceBulkImporter 0 Jul 24 18:06:29 Mac-MacBook-Air locationd[87]: Logging binary sensor data to /var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d/C/locationdSensors.bin Jul 24 18:06:29 Mac-MacBook-Air locationd[87]: Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatiblity mapping behavior in the near future. Jul 24 18:06:29 Mac-MacBook-Air blued[90]: hciControllerOnline; HID devices? 1 Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: IO80211ScanManager::getScanResult: All scan results returned for 'airportd' (pid 62). Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: IO80211ScanManager::startScanMultiple: Scan request received from 'airportd' (pid 62) (2 SSIDs, 0 BSSIDs). Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: IO80211ScanManager::startScanMultiple: Initiating scan. Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: IO80211ScanManager::getScanResult: All scan results returned for 'airportd' (pid 62). Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: IO80211ScanManager::startScanMultiple: Scan request received from 'airportd' (pid 62) (2 SSIDs, 0 BSSIDs). Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: IO80211ScanManager::startScanMultiple: Initiating scan. Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: IO80211ScanManager::getScanResult: All scan results returned for 'airportd' (pid 62). Jul 24 18:06:55 Mac-MacBook-Air networkd[176]: -[NETClientConnection effectiveBundleID] using process name mapspushd as bundle ID (this is expected for daemons without bundle ID Jul 24 18:06:55 Mac-MacBook-Air networkd[176]: -[NETClientConnection effectiveBundleID] using process name akd as bundle ID (this is expected for daemons without bundle ID Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: parseRSNIE: groupCipherType = 5 pairwiseCipherType = 5 authSel = 2 Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: initWithInterfaceAndIE: _myMacAddress 70:56:81:af:38:b5 Jul 24 18:06:55 Mac-MacBook-Air kernel[0]: setPMK: PMK SET! Jul 24 18:06:56 Mac-MacBook-Air kernel[0]: AirPort: Link Up on en0
Just to also add, after sleep, it takes a while for airport to rescan and connect to wireless.
The output from these logs was not generated by the iSCSI initiator hosted here… are you using KernSafe?
For example:
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: iscsi login 51 6500000a 3260 iqn.2017-07.com.lisa:tgt2.
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Waiting for thread exit.
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Threadid exit
Jul 24 18:06:29 Mac-MacBook-Air kernel[0]: Error to logon to iSCSI disk c0000008.
or:
18.05.43 - reboot initiated. 18.06:29 - iscsi login failed 18:06:56 - en0 up.
On Jul 24, 2016, at 11:04 PM, lulunzb notifications@github.com wrote:
Just to also add, after sleep, it takes a while for airport to rescan and connect to wireless.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iscsi-osx/iSCSIInitiator/issues/47#issuecomment-234782065, or mute the thread https://github.com/notifications/unsubscribe-auth/AEH_Q01A_AUc5ibPFLipvn5nbDo5m90Sks5qY37ugaJpZM4IDADr.
Have used both today - let me reinstall fully and will post some new ones
@lulunzb Please make sure only one is used at a time to avoid any potential conflict.
@nsinenian Now I see that: I can configure initiator-config. there is no problem. Problem is listing initiator config. It prints the default config.
And also I have errors like that: Hi, Now i have recycle of error:
(com.github.iscsi-osx.iscsid[96905]) Could not find and/or execute program specified by service: 13: Permission denied: /usr/local/libexec/iscsid (com.github.iscsi-osx.iscsid[96905]) Service setup event to handle failure and will not launch until it fires.
it is in a loop.
Hence I run uninstall script.
@kazimsarikaya Looks like there's some issue building/installing on your system with the test scripts. Here's a DMG I just built with the latest commit from the network-availability branch:
iSCSI-network-availability.zip
(Unzip then open the DMG and install as usual)
I have this issues as well. Can I test this for you?
@jaccoh Absolutely. Test and let me know how it works out. If you can test different permutations that would be great (e.g., wired connection vs wireless connection, and forced sleep - using the Apple menu - vs. normal sleep, where the machine just goes to sleep on its own).
No problem. I'll use the latest commit from that branch?
Op 10 aug. 2016 om 13:23 heeft Nareg Sinenian notifications@github.com het volgende geschreven:
@jaccoh Absolutely. Test and let me know how it works out. If you can test different permutations that would be great (e.g., wired connection vs wireless connection, and forced sleep - using the Apple menu - vs. normal sleep, where the machine just goes to sleep on its own).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Use the latest commit under the develop branch. If you have problems building let me know.
On Aug 10, 2016, at 7:39 PM, jaccoh notifications@github.com wrote:
No problem. I'll use the latest commit from that branch?
Op 10 aug. 2016 om 13:23 heeft Nareg Sinenian notifications@github.com het volgende geschreven:
@jaccoh Absolutely. Test and let me know how it works out. If you can test different permutations that would be great (e.g., wired connection vs wireless connection, and forced sleep - using the Apple menu - vs. normal sleep, where the machine just goes to sleep on its own).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iscsi-osx/iSCSIInitiator/issues/47#issuecomment-238841810, or mute the thread https://github.com/notifications/unsubscribe-auth/AEH_QyelkafT2S5hxiVPMXv1Q2LtPcY8ks5qebiLgaJpZM4IDADr.
Hello Nareg,
I'm having a problem about recovery from sleep, actually more of a request. The connection to the target itself is indeed resumed, however the filesystem on the LUN is re-mounted by OSX on a mountpoint that has nothing to do with where it was mounted before the Mac went to sleep.
Do you think there is anything that can be done about this, or is it just OSX being ... well, annoying ?
More details by email if you want them, my use case may be a bit unorthodox.
I believe that this is basically out of our control with the design that we are using.
The initiator doesn't know anything about mount points, file systems, etc. It simply relays SCSI requests between the OS and the target. It reuses all of the SCSI code (and other high level code) so from OS X.
In the scenario you are describing, from the OS viewpoint it's equivalent to hot-swapping a local SCSI drive, and the OS handles this the way it wants.
On Monday, 22 August 2016, Maxime Montinet notifications@github.com wrote:
Hello Nareg,
I'm having a problem about recovery from sleep, actually more of a request. The connection to the target itself is indeed resumed, however the filesystem on the LUN is re-mounted by OSX on a mountpoint that has nothing to do with where it was mounted before the Mac went to sleep.
Do you think there is anything that can be done about this, or is it just OSX being ... well, annoying ?
More details by email if you want them, my use case may be a bit unorthodox.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iscsi-osx/iSCSIInitiator/issues/47#issuecomment-241283158, or mute the thread https://github.com/notifications/unsubscribe-auth/AEH_Q6kcjeGHET0tgJhtSMOfz0CpjoODks5qiMKNgaJpZM4IDADr .
Yes, I thought there might have been some way for the initiator to give hints to the OS regarding how the disk should be handled.
No worries, I found a workaround :)
Hi All,
I am a new user of iSCSIInitiator and it works fine so far. My problem, however, is that if OSX wakes from sleep, the disk is lost. I read in some other thread that the connection is dropped upon sleep and restarted upon wake, but this does not seem to work. My configuration:
iscsiinitiator: iSCSIInitiator-1.0.0-beta.dmg OSX: 10.11.3 Target: FreeBSD 10.2-RELEASE
Any ideas?
TIA,
Heinrich