tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
Cloud File Storage
    Documentation
    Download PDF

    Selecting Kernels for NFS Clients

    Last updated: 2024-07-05 17:48:58
    Download PDF
      Since the NFS client is kernel-based, the bugs in some kernel versions will make the NFS service unavailable. To enjoy a better experience, please use recommended kernel versions.

      Known client issues

      No response of the file system due to kernel network stack defects (priority: high)

      For a system with a kernel version in the range of v2.6.32-696 to v2.6.32-696.10.1 (including v2.6.32-696, excluding v2.6.32-696.10.1), when the kernel requests to retry due to a busy NFS server, a kernel network stack defect may be triggered, resulting in no response to the operation. If there is no response to the operation, restart the CVM instance. For more information, see RHEL6.9:NFSv4 TCP transport stuck in FIN_WAIT_2 forever.

      No response of the file system due to kernel defects (priority: high)

      For a system with one of the following kernel versions, the NFS server failover mechanism may cause file opening, read, and write deadlocks in the NFS client, resulting in no response of the file system.
      Redhat 6, CentOS 6 2.6.32-696.3.1.el6
      All kernel versions earlier than Redhat 7 and CentOS 7 3.10.0-229.11.1.el7
      Ubuntu 15.10 Linux 4.2.0-18-generic If there is no response to the operation, restart the CVM instance. For more information, see RHEL7:NFSv4 client loops with WRITE/NFS4ERR_STALE_STATEID - if NFS server restarts multiple times within the grace period.
      For a system with one of the following kernel versions, if network reconnection occurs due to network partitioning or jitter, the NFS client may continue to have no response due to failure to handle error codes properly. The manifestation is as follows: The file system gives no response, and bad sequence-id error is repeatedly printed in the system message.
      All kernel versions earlier than Redhat 6 and CentOS 6 2.6.32-696.16.1.el6
      All kernel versions earlier than Redhat 7 and CentOS 7 3.10.0-693.el7 If there is no response to the operation, restart the CVM instance. For more information, see RHEL6/RHEL7:NFS4 client receiving NFS4ERR_BAD_SEQID drops nfs4 stateowner resulting in infinite loop of READ/WRITE+NFS4ERR_BAD_STATEID.
      For an operating system with a kernel version of CentOS/RedHat 5.11.x, executing operations ‍that require traversing a directory, such as the Is command and ‍a command containing the wildcard character * ‍or ?, will cause ‍jams or no response due to kernel defects. In this case, please upgrade the kernel to avoid this issue in the future.

      Failure to support the chown command and system call (priority: low)

      A system with a v2.6.32 kernel does not support executing the chown command and system call in the NFS client.

      Failure to terminate Is operations (priority: low)

      For a system with a kernel version of v2.6.32-696.1.1.el6 or earlier, adding and deleting files or subdirectories are also performed while Is operations are in progress, making Is operations unable to end. In this case, please upgrade the kernel to avoid this issue in the future.
      For a system with a kernel version of v4.18.0-305.12.1, Is and other directory traverse operations cannot end. Please upgrade the kernel to v4.18.0-305.12.1 to fix the issue. For more information, see Linux Kernel Archives.

      Recommended NFS images

      Linux images

      OS Type
      OS Version
      CentOS
      CentOS-6.9-x86_64: v2.6.32-696.16.1.el6.x86_64 or later
      CentOS-6.10-x86_64: v2.6.32-754.17.1.el6.x86_64 or later
      CentOS-7.2-x86_64: v3.10.0-514.26.2.el7.x86_64 or later
      CentOS-7.3-x86_64: v3.10.0-514.26.2.el7.x86_64 or later
      CentOS-7.4-x86_64: v3.10.0-693.2.2.el7.x86_64 or later
      CentOS-7.5-x86_64: v3.10.0-862.14.4.el7.x86_64 or later
      CentOS-7.6-x86_64: v3.10.0-957.21.3.el7.x86_64 or later
      CentOS-7.7-x86_64: v3.10.0-1062.18.1.el7.x86_64 or later
      CentOS-8.-x86_64: 4.18.0-147.5.1.el8_1.x86_64 or later
      Tencent OS Linux
      TencentOS Server 2.2 (Tkernel 3)
      TencentOS Server 2.4 (Tkernel 4)
      TencentOS Server 2.6 (Final)
      TencentOS Server 3.1 (Tkernel 4)
      Debian
      Debian-9.6-amd64: v4.9.0-8-amd64 or later
      Debian-9.8-amd64: v4.9.0-8-amd64 or later
      Debian-9.10-amd64: 4.9.0-9-amd64 or later
      Ubuntu
      Ubuntu-14.04-amd64: v4.4.0-93-generic or later
      Ubuntu-16.04-amd64: v4.4.0-151-generic or later
      Ubuntu-18.04-amd64: v4.15.0-52-generic or later
      Ubuntu-20.04-amd64: v5.4.0-31-generic or later
      OpenSuse
      OpenSuse-42.3-x86_64: v4.4.90-28-default or later
      SUSE
      Enterprise Server 12 SP2 x86_64: v4.4.74-92.35-default or later
      Enterprise Server 12 SP4 x86_64: v4.12.14-95.16-default or later
      CoreOS
      CoreOS-1745.7.0_64: v4.19.56-coreos-r1 or later
      CoreOS-2023.4.0_64: v4.19.56-coreos-r1 or later

      Windows images

      OS Type
      OS Version
      Windows Server 2012
      Windows Server 2012 R2 Datacenter 64-bit Chinese
      Windows Server 2012 R2 Datacenter 64-bit English
      Windows Server 2016
      Windows Server 2016 DataCenter 64-bit Chinese
      Windows Server 2016 Datacenter 64-bit English
      Windows Server 2019
      Windows Server 2019 Datacenter 64-bit Chinese
      Windows Server 2019 IDC 64-bit English
      
      
      
      Contact Us

      Contact our sales team or business advisors to help your business.

      Contact Us
      Technical Support

      Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy