Bug 238413 - [NetApp-S 4.6 feat] iscsi lun resize dosen't take effect without a restart
Summary: [NetApp-S 4.6 feat] iscsi lun resize dosen't take effect without a restart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 4.6
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Mike Christie
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 217206
TreeView+ depends on / blocked
 
Reported: 2007-04-30 12:03 UTC by Ritesh Raj Sarraf
Modified: 2018-10-20 00:41 UTC (History)
5 users (show)

Fixed In Version: RHBA-2007-0810
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-15 16:12:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rescan devices (994 bytes, patch)
2007-07-31 05:00 UTC, Mike Christie
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0810 0 normal SHIPPED_LIVE iscsi-initiator-utils bug fix update 2007-11-14 18:40:17 UTC

Description Ritesh Raj Sarraf 2007-04-30 12:03:39 UTC
Description of problem:

Currently, when resizing a LUN on the filer, from say 40G to 50G, the changes 
aren't reflected on the host.
For example, you started the iscsid daemon and mapped a LUN of size 40G.
Then you resize the LUN on the filer to 50G. Now if you reload the iscsi 
service, still the LUN is reported of size 40G on the host.
To get the newly updated size  a restart of the iscsid daemon is required 
which is disruptive is other LUNs are also mapped and mounted.


Version-Release number of selected component (if applicable):
RHEL4 U4/U5

How reproducible:
Very Reproducible

Steps to Reproduce:
1. Start the iscsid service mapping a LUN.
2. Now resize the LUN on the filer.
3. Do an iscsi reload on the host.
4. The LUN size reported is still the old size
  
Actual results:
The LUN is still reported to be of the older size.

Expected results:
The new LUN size should be reported on a reload

Comment 1 Andrius Benokraitis 2007-04-30 18:09:13 UTC
bug 238414 is a corresponding bug for RHEL 5.1.

Comment 2 RHEL Program Management 2007-05-08 20:26:06 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 5 Andrius Benokraitis 2007-07-26 13:43:34 UTC
This is dangerously close to moving to RHEL 4.7. This is a non-trivial feature
request with little info/business case.

Comment 6 Mike Christie 2007-07-31 05:00:35 UTC
Created attachment 160293 [details]
rescan devices

Here is a real simple patch, which does the basics.

You can either run iscsi-rescan by hand to pick up the size changes or you can
run "service iscsi reload".

This just echos into the /sys/block/sdX/device/rescan attribute. So the user
still needs to do whatever admin task they need to do before rescanning. For
example the app may have to reread the new size or the FS may have to be
unmounted and remounted.

Comment 12 John Poelstra 2007-08-29 04:30:18 UTC
A fix for this issue should have been included in the packages contained in the
RHEL4.6 Beta released on RHN (also available at partners.redhat.com).  

Requested action: Please verify that your issue is fixed to ensure that it is
included in this update release.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to FAILS_QA.

If you cannot access bugzilla, please reply with a message to Issue Tracker and
I will change the status for you.  If you need assistance accessing
ftp://partners.redhat.com, please contact your Partner Manager.

Comment 13 John Poelstra 2007-09-05 22:24:01 UTC
A fix for this issue should have been included in the packages contained in 
the RHEL4.6-Snapshot1 on partners.redhat.com.  

Requested action: Please verify that your issue is fixed to ensure that it is 
included in this update release.

After you (Red Hat Partner) have verified that this issue has been addressed, 
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent 
symptoms of the problem you are having and change the status of the bug to 
FAILS_QA.

If you cannot access bugzilla, please reply with a message about your test 
results to Issue Tracker.  If you need assistance accessing 
ftp://partners.redhat.com, please contact your Partner Manager.

Comment 15 errata-xmlrpc 2007-11-15 16:12:45 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0810.html



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