We're also having this problem. Just wondering if there's been any update?

Mounting the PowerPath devices with "_netdev" option permits boot-time fsck on PowerPath pseudo-devices (and also on Logical Volumes created out of PowerPath pseudo-devices). The fsck is performed by S25netfs after network services are up (PowerPath is already started by then).

The fsckorder (6th column on /etc/fstab) may be marked as necessary (a value greater than 0 performs boot-time fsck).

Sample /etc/fstab file:
-----------------------
/dev/VolGroup00/LogVol01 / ext3 defaults 1 1
/dev/emcpowerl /mnt/mnta ext2 _netdev 0 2
/dev/emcpowerd /mnt/mntb ext3 _netdev 0 0
/dev/vg_emcp_xov/lvol0 /mnt/mnto ext2 _netdev 0 3

/dev/vg_emcp_xov/lvol0 is a LV created out of PowerPath pseudo-devices.

It needs to be documented that PowerPath devices should be mounted with "_netdev" option in /etc/fstab to permit boot-time fsck.

The documentation will be updated to reflect this.

Paul,

is _netdev requirement something new that has to be done with PP5, we have never used _netdev with PP4.5 ..but i wonder if this is something we have to pay attention to when we upgrade to PP5.

Thanks

Dynamox, this is specific to version 5.x

This issue has been documented in the Linux 5.1 Release Notes;

These are not available on powerlink as yet..

Message was edited by:
PaulCork

Thank you

The PP5.1 release notes are now available on PowerLink: from p30:
===
The _netdev option in /etc/fstab
PowerPath devices should be mounted with "_netdev" option in
/etc/fstab to permit boot-time fsck. For RHEL 5 and 5.1, in an iSCSI
setup, PowerIscsi is run as service S24. This configures the PowerPath
devices and makes them available to S25netfs to perform fsck on
them.
===

CB,

does it also apply to RHEL 4 with Powerpath 5.1 ?

Thanks

Hi Dynamox,

the Release notes are non-specific regarding RHEL version, I have checked the OPT that this bug was reported to EMC and it was on the RHEL5 platform... I will do more reseach into previous cases and see if RHEL4 is affected the same way... Will update you shortly.

great ..thank you

This seems on only affect RHEL5 with PowerPath 5.x. No previous cases with RHEL4 or earlier...

great ..thank you for verifying that.