VMware VDR Ext3-fs warning: Checktime reached, running e2fsck is recommanded

VMware VDR Ext3-fs warning: Checktime reached, running e2fsck is recommended

 

 

vmware vdr를 운영중, 제목와 같은 메세지가 나타날때가 있다.

ext3파일시스템의 경고와 합께 파일시스템을 체크하라고 친절하게 나타난다.

 

VDR 어플라이언스는 리눅스 기반 가상머신이다.

리눅스 운영체제가 설치된 EXT3파일시스템이 탑재되는 시점마다 지정된 파일시스템을 체크하도록 요구된다.

파일시스템을 마운트하여 지정된 수 이상의 파일시스템을 확인하지 않은 경우 문제가 발생한다.

 

 

Booting VMware Data Recovery fails with the error: ext3-fs warning: maximal mount count reached reported on boot (1020974)

Symptoms

·    Unable to boot VMware Data Recovery (VDR)

·    Restore points are not detected

·    Running an integrity check fails

·    Booting VDR fails with the error:

ext3-fs warning: maximal mount count reached, running e2fsck is recommended

·    In the /var/log/messages log file of the VDR appliance, you see the entry: 

ext3-fs warning: checktime reached, running e2fsck is recommended

Cause

The VDR appliance is based on a Linux virtual machine. The ext3 file system on which the Linux operating system is installed requires you to check the file system once in every specified number of times that it is mounted. This issue occurs if you have not verified the filesystem beyond the specified number of filesystem mounts.

Resolution

For VDR to detect the restore points, you must perform a file system check on the file system.

 

To check the filesystem:

1. Log in to the console of the VDR appliance as the root user

2. To determine the block device to be checked, run this command against the /var/log/messages file:

# grep -A 1 e2fsck /var/log/messages

You see an output similar to:

# kernel: EXT3-fs warning: checktime reached, running e2fsck is recommended
# kernel: EXT3 FS on sdb1, internal journal

From the output, you can see that /dev/sdb1 is the device to be checked.

3. Run this command to boot VDR in single user mode:

# init 1

4. Run this command to unmount the filesystem:

# umount /dev/sdb1

5. Run this command to perform a filesystem check on the block device found in Step 1:

# e2fsck -n /dev/sdb1

Note: The -n option ensures that the changes are not written to disk. 
Note: If the e2fsck command says there is an issue with the file system is can be corrected with: 

# e2fsck /dev/sdb1 

6. Run this command to reboot the appliance in normal mode:

# init 6

7. Verify /var/log/messages log to see if the error is reported again.