Hello Charalampos, > http://pastebin.com/AqqJaYVX > May 20 12:30:32 iscsi-machine kernel: [406849.747117] ABORT_TASK: Found referenced iSCSI task_tag: 284671 > May 20 12:30:32 iscsi-machine kernel: [406849.747120] ABORT_TASK: ref_tag: 284671 already complete, skipping > May 20 12:30:32 iscsi-machine kernel: [406849.747122] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 284671 > May 20 12:30:32 iscsi-machine kernel: [406849.747890] ABORT_TASK: Found referenced iSCSI task_tag: 284684 > ... > May 20 12:38:21 iscsi-machine kernel: [407318.824922] TARGET_CORE[iSCSI]: Detected NON_EXISTENT_LUN Access for 0x000000ce I saw once the same error, but was not able to reproduce it. For it happened approx after 5 days of use. I don't know if the Debian Linux Kernel is build with debugging enabled, but if it is can you enable debugging and send some data to the list so that Nab or someone else can identify the reason for the error? .config CONFIG_DYNAMIC_DEBUG=y echo 'module iscsi_target_mod +p' > /sys/kernel/debug/dynamic_debug/control echo 'module target_core_pscsi +p' > /sys/kernel/debug/dynamic_debug/control echo 'module target_core_file +p' > /sys/kernel/debug/dynamic_debug/control echo 'module target_core_iblock +p' > /sys/kernel/debug/dynamic_debug/control echo 'module target_core_mod +p' > /sys/kernel/debug/dynamic_debug/control can you tell us a little bit more of your setup: - How many ESX servers are accessing your LUN? - Which ESX version do you use? - Can you reproduce the issue? - After how many days did the issue show up? I'm asking because I tried like crazy to reproduce the issue, but was not able to do so outside a production environment, so I gave up. But maybe I should have just let it running a few days with a few VMs powered on, on it. Cheers, Thomas -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
