Bug 232396 - [NetApp 5.1 bug] LVM doesn't work with iSCSI
[NetApp 5.1 bug] LVM doesn't work with iSCSI
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: device-mapper (Show other bugs)
All Linux
urgent Severity medium
: ---
: ---
Assigned To: Mike Christie
Corey Marthaler
: Reopened
Depends On:
Blocks: 217207
  Show dependency treegraph
Reported: 2007-03-15 03:16 EDT by Ritesh Raj Sarraf
Modified: 2010-01-11 21:17 EST (History)
17 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-24 06:27:04 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 Ritesh Raj Sarraf 2007-03-15 03:16:02 EDT
Description of problem:
Currently it is not possible to use LVM on top of iSCSI devices. Basically, 
LVM initialization happens during disk initialization, which is right at the 
start of init. Where as the network and iSCSI (also multipath) services start 
way later. Hence, without iSCSI being started, LVM is not able to initialize 
the PVs because iscsid isn't started and no LUNs are mapped to the host.

There is a work around to this issue by manually re‑scanning the PVs after
the OS has completely booted. But this will be a problem if there are 
applications which are configured to use the LV as their data path because 
the applications will start automatically on system startup and will fail by 
not finding the Logical Volume/Mount Point.

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

How reproducible:

Steps to Reproduce:
1. Configure iSCSI and map some LUNs to the host
2. Create a VG/LV on top of those LUNs
3. Set them to auto-mount at boot.
4. Upon boot, the devices aren't mounted because the PV/VG aren't seen to the 
Actual results:
Logical Volumes are not found because the LUN was not mapped at the time of 
LVM initialization which further leads to failure of mount points which are 
part of LVM

Expected results:
Device-Mapper should have the ability to do an LVM re-scan when it senses that 
a new block device has been plugged in.

Additional info:
This isn't specific to iSCSI. Can be reproducible with any block device 
providing application which starts-up in init after LVM initialization is 
Comment 2 Mike Christie 2007-05-07 12:42:26 EDT
Did you try to add the _netdev option to fstab? There is some check in the netfs
 script where if it is set, then it kicks off /sbin/lvm.static vgscan.
Comment 3 Andrius Benokraitis 2007-05-17 09:52:46 EDT
Per NetApp, more testing will be done on this, but outlook is good on testing
the GA RHEL 5 version.
Comment 4 Wolfram Richter 2007-05-23 08:10:13 EDT
The _netdev option might help. Except with GFS2 where the _netdev option leads
to a mount error.
Workaround here: Change gfs2 init.d script to include vgchange -ay before mount. 
Comment 5 Tom Coughlan 2007-06-15 14:06:16 EDT
Please let us know whether the solution in commet 2 or 4 resolve this problem. 
Comment 6 Ritesh Raj Sarraf 2007-06-26 02:28:03 EDT
Thanks. The issue is resolved with the option mentioned in Comment #2.
Closing the bug.

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