Bug 228815 - Rebooting with iSCSI target disks mounted results gets stalled.
Rebooting with iSCSI target disks mounted results gets stalled.
Status: CLOSED DUPLICATE of bug 228814
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: iscsi-initiator-utils (Show other bugs)
5.0
All Linux
medium Severity high
: ---
: ---
Assigned To: Tom Coughlan
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-15 04:19 EST by Shyam kumar Iyer
Modified: 2008-04-07 01:14 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-15 04:28:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Shyam kumar Iyer 2007-02-15 04:19:59 EST
Description of problem:
iSCSI target disks are mounted on the Server. On rebooting the server the 
reboot stops at synchronizing SCSI cache for the iSCSI target disk. iSCSI 
initiator connection times out and following message is displayed-
"iscsi: can not broadcast skb (-3)"
"connection0:0 iscsi: detected conn error (1011)"


Version-Release number of selected component (if applicable):
iscsi-initiator-utils-6.2.0.742-0.5.el5

How reproducible:
Always.

Steps to Reproduce:
1. Initiate iSCSI initiator.
2. Mount iSCSI target's disk.
3. Reboot the system.
  
Actual results:
Reboot stalls at Sychronizing SCSI cache for the iSCSI target's disk.

Expected results:
Reboot should not stall.

Additional info:
Looks like since the network is stopped before the disks are unmounted the 
synchronize SCSI cache command fails obviously because of the network not 
being up.
Comment 1 Shyam kumar Iyer 2007-02-15 04:28:39 EST
Somehow bugzilla shows that the product selected is invalid and I am compelled 
to resubmit the bug again. Now, I have 2 bugs with the same description. 
This bug is the same as 228814. Marking it as duplicate.

*** This bug has been marked as a duplicate of 228814 ***

Note You need to log in before you can comment on or make changes to this bug.