Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 127389 - Unable to work with HP EVA3000 'snapclone' LUN using qla2300 driver
Unable to work with HP EVA3000 'snapclone' LUN using qla2300 driver
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2004-07-07 11:57 EDT by Mimmus
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-07 12:49:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mimmus 2004-07-07 11:57:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040614 Firefox/0.8

Description of problem:
I'm unable to work with LUNs created with 'snapclone' add-on of
EVA3000 disk-array using qla2300 driver included in
kernel-2.4.21-15.0.3.ELhugemem .
I rescanned LUNs (and rebooted server too): I'm able to see the new
LUN but 'fdisk /dev/sdb' says 'Unable to read /dev/sdb'.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a LUN, 'fdisk' and 'mkfs' it
2. Rescan LUNs using usual methods or rebooting server
3. Mount LUN
4. Generate a 'snapclone' of this LUN using EVA CommandView
5. Rescan LUNs using usual methods or rebooting server
6. See new LUN
7. Try to mount or 'fdisk' new LUN

Actual Results:  Unable to see 'clone' LUN

Expected Results:  Directly mount clone LUN without problems

Additional info:

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