Bug 175346
| Summary: | Ading more number iSLB initiator target leads segmenationfault on initia | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Srinivasan <srinivkr> |
| Component: | iscsi-initiator-utils | Assignee: | Mike Christie <mchristi> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | CC: | cgodavar, smitha.narayan |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-01-10 17:45:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
What is islb? Does iscsid seg fault? Is there any /var/log/messages or dmesg output? |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description of problem: Description: Setup: two MDS boxes(9216) connected with FC cable.And cfs enabled and iSLB distribute enabled on it.Configured the islb initiator with ip-address which is an linux initiator.And initially added one initiator target under this, and did iSLB commit.This initiator target configuration done with out fclun and iscsi lun.And again added one initiator target under the same initiator{This initiator target configuration done with out fclun and iscsi lun} ,and did iSLB commit. Version-Release number of selected component (if applicable): 2.4.20-8smp How reproducible: Always Steps to Reproduce: 1.Configure islb initiator with ip-address and add an islb initiator target 2.Do islb commit and after that again add an islb initiator target with pwwn and do islb commit 3. Go to linux initiator and restart iscsi u will get an segmentation fault .This is happenening with JBOD as end device and if it is MSA it is happening after adding more than 3 initiator targets Actual Results: It is giving Segmentation Fault after adding more than two initiator targets Expected Results: It should display the number of islb initiator targets configured for the initiator Additional info: