<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>NFS on </title>
    <link>https://peng.fyi/tags/nfs/</link>
    <description>Recent content in NFS on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>map[name:Peng Zhang]</managingEditor>
    <webMaster>map[name:Peng Zhang]</webMaster>
    <copyright>Peng Zhang</copyright>
    <lastBuildDate>Mon, 09 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://peng.fyi/tags/nfs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remount sysfs to make its superblock rw: mount -o remount,rw /sys</title>
      <link>https://peng.fyi/post/sysfs-superblock-race/</link>
      <pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate>
      <author>map[name:Peng Zhang]</author>
      <guid>https://peng.fyi/post/sysfs-superblock-race/</guid>
      <description>
        
          
            While testing Amazon EFS volumes in containers, I found that sequential reads in some runs were about 4 times slower than in others. EFS volumes are mounted with efs-utils, which turns mount -t efs into an NFSv4.1 mount through a local TLS proxy. In the slow runs, the NFS mount&#39;s read_ahead_kb was 128 instead of 15360.
That symptom has a known cause. Linux 5.4 dropped the default NFS readahead from 15 times rsize, which is 15 MiB with EFS&#39;s 1 MiB rsize, to 128 KiB (NFS: Optimise the default readahead size).
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
