IT24290: MOUNTV105_START.KSH COULDN'T DETERMINE FILESYSTEM TYPE AND FINALLY ATTEMPT TO "FSCK -P".

Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as fixed if next.

Error description

• check GPFS log, found following messages occuried once
  per second:
  Fri Aug 11 16:21:57 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2909:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:21:58 CST 2017: mountV105_start.ksh[32012]: check
  GPFS log, found following messages occuried once
  per second:
  Fri Aug 11 16:21:57 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2909:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:21:58 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2910:
  Will fsck /dev/db2fs1
  Fri Aug 11 16:21:58 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2910:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:21:59 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2911:
  Will fsck /dev/db2fs1
  Fri Aug 11 16:21:59 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2911:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:22:00 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2912:
  Will fsck /dev/db2fs1
  Fri Aug 11 16:22:00 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2912:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:22:01 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2913:
  Will fsck /dev/db2fs1
  Fri Aug 11 16:22:01 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2913:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:22:02 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2914:
  Will fsck /dev/db2fs1
  Fri Aug 11 16:22:02 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2914:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:22:03 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2915:
  Will fsck /dev/db2fs1
  Fri Aug 11 16:22:03 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2915:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:22:04 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2916:
  Will fsck /dev/db2fs1
  Fri Aug 11 16:22:04 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2916:
  fsck /dev/db2fs1 returns 8
  Fri Aug 11 16:22:05 CST 2017: mountV105_start.ksh[32012]:
  Attempt 2917:
  Will fsck /dev/db2fs1
  From the mountV105_start.ksh script, the following sequence is
  triggering fsck:
  If filesystem not mounted: (if [ ${mounted} -gt 0 ];
  then...else)
     Attempt to mount filesystem (mount ${MP})
     If mount failed: (   if [ $rc -eq 0 ] ; then)
        Check for filesystem type of target filesystem: (      if
  [[ $fstype == "gpfs" ]] ; then)
           Couldn't determine filesystem type: (else)
              Attempt to fsck disk (fsck -f -p ${blockDevice?})
                This will keep retring to fsck the disk as long
  as fsck fails. (while [[ $rc -ne 0 ]]; do)
  

Local fix

• gnore the error message in gpfs log
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * pureScale                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to db2_v111m3fp3 or higher level                     *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• RB10 PSN

     UP

• RB10 PSY

     UP