Exadata X3-2 Hardware
 
Exadata X4-2 Hardware
 
Exadata Database Machine X2-8
 
Exadata X3-8 Hardware
 
Exadata Database Machine X2-2 Hardware
 
Exadata Database Machine V2
 

PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
 

Applies to:

Symptoms

 Exachk shows:
=============

1 - Database server disk devices tune2fs check interval should be set to 0
2 - The database server disk devices should have "Maximum mount count" equal to "-1"

Cause

 You can ignore the false values in exack as it is a bug with exachk which gives wrong result. <Bug 18474024> (duplicate of unpublished bug 18329202)

Solution

The next release (2.2.5) of exachk is expected to have this issue fixed

To manually verify these two checks, as the root userid, download the attached scripts to the database servers in question, make them executable and execute them as the root userid:

1) manual_mnt_cnt.sh
2) manual_chk_int.sh

For example:

./manual_mnt_cnt.sh

./manual_chk_int.sh

If the manual validation script results show that the "Check interval" and "Maximum mount count" as below then they are set as recommended.

[root@gerexadbadm01 tmp]# ./manual_chk_int.sh

SUCCESS:  All database server disk devices found (other than swap) and the boot device had "Check interval" equal to 0
Boot Device /dev/sda1: 0
/dev/VGExaDb/LVDbSys1: 0
/dev/VGExaDb/LVDbSys2: 0
/dev/VGExaDb/LVDbOra1: 0


[root@gerexadbadm01 tmp]# ./manual_mnt_cnt.sh

SUCCESS:  All database server logical volumes found (other than swap) and the boot device had "Maximum mount count" equal to -1
Boot Device /dev/sda1: -1
/dev/VGExaDb/LVDbSys1: -1
/dev/VGExaDb/LVDbSys2: -1
/dev/VGExaDb/LVDbOra1: -1

References

This solution has no attachment