Overview
This article provides information on how to troubleshoot File System Errors in Kerio Connect Unix (Linux or macOS) installations.
The customers may report file system errors and may have entries in the dmesg section of the Support Information file, which look similar to the entries provided below.
[5257894.127171] JBD2: Spotted dirty metadata buffer (dev = sdb1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
[5247762.655351] EXT4-fs error (device sdb1): ext4_free_inode:346: comm mailserver: bit already cleared for inode 132258056
[5247762.710642] EXT4-fs error (device sdb1): mb_free_blocks:1457: group 16145, block 529047161:freeing already freed block (bit 7801); block bitmap corrupt.
[5247762.710840] EXT4-fs error (device sdb1): ext4_mb_generate_buddy:757: group 16145, block bitmap and bg descriptor inconsistent: 8098 vs 8099 free clusters
[5248113.100444] EXT4-fs error (device sdb1): mb_free_blocks:1457: group 14786, block 484532860:freeing already freed block (bit 25212); block bitmap corrupt.
[5248113.100614] EXT4-fs error (device sdb1): ext4_mb_generate_buddy:757: group 14786, block bitmap and bg descriptor inconsistent: 7801 vs 7803 free clusters
[5257894.126992] EXT4-fs error (device sdb1): ext4_mb_generate_buddy:757: group 16159, block bitmap and bg descriptor inconsistent: 6576 vs 7217 free clusters
Root Cause
The mount point/disk is corrupt.
Process
Please follow the steps below to troubleshoot these errors.
-
Follow the instructions in the Troubleshooting Performance issues article to eliminate the customer's environmental store issues.
-
If the errors appear even after cleaning-up the folders, please advise the customer to re-install Kerio Connect, by following the steps below.
-
Download the relevant version of Kerio Connect from Kerio Software Archive.
-
If the errors are still not resolved, then the disk/mounting point should be repaired or replaced.