Bug 198794 - VGs on zSeries zfcp storage not activated at boot
Summary: VGs on zSeries zfcp storage not activated at boot
Status: CLOSED DUPLICATE of bug 189494
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: initscripts
Version: 4.0
Hardware: s390
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-13 16:20 UTC by Bryn M. Reeves
Modified: 2014-03-17 03:00 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-07-13 17:30:31 UTC


Attachments (Terms of Use)
proposed patch to rc.sysinit (559 bytes, text/x-patch)
2006-07-13 16:28 UTC, Bryn M. Reeves
no flags Details

Description Bryn M. Reeves 2006-07-13 16:20:29 UTC
Problem Description
-------------------
On zSeries machines, zSeries Fibre Channel Adapter devices are brought online by
the zcfpconf.sh script provided in s390utils:

[ -x /sbin/zfcpconf.sh ] && /sbin/zfcpconf.sh

This is called from rc.sysinit after initial LVM setup completes so any LVM PVs
present on zfcp devices are not discovered by the initial vgscan/vgchange.

A second pass LVM init is carried out, but only if an /etc/mdadm.conf file for
Software RAID exists.


Steps to reproduce
------------------
1. Create an LVM2 volume group on zfcp attached storage
2. Confirm the VG is accessible
3. Reboot the system
4. Run vgs or vgdisplay

Actual Result:
The VG on zfcp storage is not shown.

Expected Result:
The VG on zfcp storage is activated at boot.

Comment 1 Bryn M. Reeves 2006-07-13 16:28:09 UTC
Created attachment 132384 [details]
proposed patch to rc.sysinit

Proposed patch to rc.sysinit attached:

- Move mdadm-specifics out of 2nd pass LVM activation 
- Add check for /etc/multipath.conf before mp initialization
- Add check for /etc/zfcp.conf to 2nd pass LVM activation

Comment 2 Bill Nottingham 2006-07-13 17:29:29 UTC
Why not just move it earlier?

Comment 3 Bill Nottingham 2006-07-13 17:30:31 UTC

*** This bug has been marked as a duplicate of 189494 ***


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