Failed to check TiDB cluster status: mount point / does not have 'nodelalloc' option set

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 检查tidb集群状态出现失败，mount point / does not have ‘nodelalloc’ option set

| username: TiDBer_新手

[TiDB Usage Environment] Single machine with multiple instances simulating a production environment
[TiDB Version] v7.5.0
[Reproduction Path]
When adding a data disk with EXT4 file system mount parameters on the target machine where TiKV is deployed,
if the mount parameters do not include nodelalloc, it means it has not taken effect.

Using the command tiup cluster check ./topology.yaml --apply --user k8soperator -p
Input SSH password:

  • Cleanup check files on 192.168.36.61:22 … Done
    Node Check Result Message

192.168.36.61 cpu-cores Pass number of CPU cores / threads: 4
192.168.36.61 memory Pass memory size is 16384MB
192.168.36.61 disk Warn mount point / does not have ‘noatime’ option set, auto fixing not supported
192.168.36.61 disk Warn mount point /cubd/tidb1 does not have ‘noatime’ option set, auto fixing not supported
192.168.36.61 disk Warn mount point /cubd/tidb4 does not have ‘noatime’ option set, auto fixing not supported
192.168.36.61 thp Pass THP is disabled
192.168.36.61 command Pass numactl: policy: default
192.168.36.61 os-version Pass OS is CentOS Linux 7 (Core) 7.9.2009
192.168.36.61 cpu-governor Warn Unable to determine current CPU frequency governor policy, auto fixing not supported
192.168.36.61 network Pass network speed of cali180eff2222a is 10000MB
192.168.36.61 network Pass network speed of cali3b166e8a736 is 10000MB
192.168.36.61 disk Fail mount point /cubd/tidb1 does not have ‘nodelalloc’ option set, auto fixing not supported
192.168.36.61 disk Fail mount point /cubd/tidb4 does not have ‘nodelalloc’ option set, auto fixing not supported
192.168.36.61 selinux Pass SELinux is disabled

  • Try to apply changes to fix failed checks

Snipaste_2024-02-05_16-28-39
Snipaste_2024-02-05_16-28-39943×322 11.5 KB

mount point / does not have 'nodelalloc' option set

How to troubleshoot and resolve this error?
[Encountered Problem: Problem Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page

fstab
fstab698×324 9.21 KB

[Attachments: Screenshots/Logs/Monitoring]

2
| username: db_user | Original post link
3
| username: TiDBer_新手 | Original post link

Adding nodelalloc to the fstab file and using mount -t ext4 does not take effect.

4
| username: 小龙虾爱大龙虾 | Original post link

mount -t ext4 -o remount

5
| username: TIDB-Learner | Original post link

First unmount, then mount. Remember to add this parameter.

6
| username: dba远航 | Original post link

Please post the contents of your fstab file for us to take a look.

7
| username: TiDBer_新手 | Original post link

It has already been pasted.

8
| username: zhanggame1 | Original post link

Have you run mount -a? Check with df -h to see if it’s mounted.

9
| username: 数据库真NB | Original post link

There is no mount point with this name, right?

10
| username: 哈喽沃德 | Original post link

After making changes, run mount -a.

11
| username: Soysauce520 | Original post link

Have you remounted?

12
| username: TiDBer_新手 | Original post link

How exactly do you add nodelalloc to mount? I found information saying that the nodelalloc parameter is not supported. Is it implemented like this below, using the mount command with the nodelalloc option for each partition? Since the standard mount command does not directly provide the nodelalloc option, you can achieve a similar effect through kernel parameters like noatime,nodiratime,nobarrier,noinit_itable,nodelalloc. For the ext4 file system, you can try using the data=writeback parameter instead of nodelalloc, as they may have similar effects in some cases.

Bash

1sudo mount -t ext4 -o noatime,nodiratime,nobarrier,data=writeback /dev/vdb1 /mnt/data1
2sudo mount -t ext4 -o noatime,nodiratime,nobarrier,data=writeback /dev/vdb2 /mnt/data2
3sudo mount -t ext4 -o noatime,nodiratime,nobarrier,data=writeback /dev/vdb3 /mnt/data3
4sudo mount -t ext4 -o noatime,nodiratime,nobarrier,data=writeback /dev/vdb4 /mnt/data4
5sudo mount -t ext4 -o noatime,nodiratime,nobarrier,data=writeback /dev/vdb5 /mnt/data5

If you indeed need the nodelalloc feature and your file system and kernel support this option, please refer to the specific file system documentation or kernel documentation to get the correct mount parameters.

Additionally, to persist the settings in /etc/fstab, you can write it like this:

1# Example content (replace with actual UUID)
2UUID=<vdb1_UUID>    /mnt/data1    ext4    defaults,noatime,nodiratime,nobarrier,data=writeback 0 0
3UUID=<vdb2_UUID>    /mnt/data2    ext4    defaults,noatime,nodiratime,nobarrier,data=writeback 0 0
4UUID=<vdb3_UUID>    /mnt/data3    ext4    defaults,noatime,nodiratime,nobarrier,data=writeback 0 0
5UUID=<vdb4_UUID>    /mnt/data4    ext4    defaults,noatime,nodiratime,nobarrier,data=writeback 0 0
6UUID=<vdb5_UUID>    /mnt/data5    ext4    defaults,noatime,nodiratime,nobarrier,data=writeback 0 0
13
| username: TiDBer_新手 | Original post link

Uninstalling the disk, formatting it, and remounting it with parameters have already taken effect. Thank you.

14
| username: zhanggame1 | Original post link

What did you refer to for the installation? Following the official documentation and copying each step with the data disk shouldn’t cause any issues.

TiDB Environment and System Configuration Check | PingCAP Documentation Center

15
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.