Emergency UNIX and Linux Support

All the EMC PowerPath stuff should be loaded nice and early via /etc/modprobe.conf.pp - you can try disabling fscks (change the 2 to 0 for all SAN-based FS) but it *shouldn't* make a difference.

Found a couple of posts with people having similar issues to you - one of which was unanswered and one was identified as an EMC bug - the EMC solution?! - comment out and mount manually!

If you do end up doing that, I'd suggest adding the mount entries to /etc/rc.local.

However, in the first instance, I'd get a support case open with EMC ASAP and double check for changes on the system. Have there been any upgrades recently (kernel, for example)?

I will need to take downtime to test changes of fsck from 2 to 0. I will think it later, once I have something in my hand.
There were no recent changes made on this system. However, this server was rebooted after very long time, so we didn't knew if this is new problem or it was exist there and we didn't knew. I will try to get hold of EMC guys.

You'll probably find it was the result of some change made in the very long time prior to the server being rebooted and prior to the problem being discovered.

Let us know how you go with EMC!

Cheers,
ZB

I got response from EMC.
"In the /etc/fstab file , PowerPath devices should be mounted with the _netdev option instead of the defaults option. This will ensure that fsck is run later in the boot sequence"
This should work I think.

That will definitely work - and checking my notes, is exactly what I used to do with OCFS2 filesystems under Linux.

My filesystems are reiserfs. Should this option work with that also ?

It should still work - the _netdev mount option should be independent of the filesystem type. However - your initial /etc/fstab shows them as being ext3 filesystems? In any case, _netdev should do the trick.