Bug 56976
Summary: | [qlogic] Qlogic lun is "not a valid block device" after reboot | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Clay Cooper <clay_cooper> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | afom_m, dale_kaisner, danny_trinh, dean_oliver, gary_lerhaupt, john_hull, matt_domsch, michael_e_brown, rogelio_noriega |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-12-06 16:35:22 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: |
Description
Clay Cooper
2001-12-01 21:39:41 UTC
I've seen this before but cannot reproduce it with the current driver (2.4.9-17.4) Reproduced w/ 2.4.9-17.4smp >How reproducible: >Always > >Additional comment by arjanv > >I've seen this before but cannot reproduce it with the current driver >(2.4.9-17.4) > >Additional comment by clay_cooper > >Reproduced w/ 2.4.9-17.4smp Does it happen every time now? If not, can you characterize this? I just tried this 4 times (fdisk /dev/sdX, make partition, mke2fs, mount, put file on, umount, reboot) and I could mount and read the file just fine after reboot.... To clarify, our tests were done with a PV650 direct-attached. We did the same tests earlier using the switched fabric. We could not reproduce the problem with either setup. Sounds like we need more explicit setup information; we have duplicated as exactly as we can, with no luck reproducing it. Ever since I created partitions, filesystems, and mounted all ten luns on my attached storage I have not been able to reproduce this. Several reboots and different combinations of mounting and rebooted, and still nothing. I have not see this since the very first check after installing 2.4.9-17.4smp. I will keep an eye out for this, but it appears to be all but gone. So the first boot must have been a leftover from the previous kernel. I'll close this; re-open it if you see it again with 17.4 or later. |