Edition of Tuesday 10 November 2026

Remount sysfs to make its superblock rw: mount -O remount,rw /sys

Comments on “Remount sysfs to make its superblock rw: mount -O remount,rw /sys”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Engineer Peng Zhang traced a fourfold variance in Amazon EFS sequential read speed to a sysfs race. Containers in one network namespace share a single sysfs superblock, and whichever mounts first sets it ro or rw. If an unprivileged container goes first, efs-utils' privileged container can't write read_ahead_kb, leaving 128 KiB instead of 15 MiB. The proposed fix is mount -o remount,rw /sys. The kernel-behavior claims come from the author's source reading and a test script, and several weren't independently verified.

Read the original at peng.fyi. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 17 of 95 with a score of 0.63. The panel rated it highest on technical depth (0.96) and new information (0.91), lowest on audience breadth (0.44). Placed No. 17, No. 42 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed kernel-level debugging of sysfs superblock sharing across containers causing slow EFS reads; strongly technical and substantiated, narrow audience but actionable for container and infra builders.
AI judgeJudge 3gpt-5.6-luna
A highly substantiated, reproducible Linux/container engineering investigation explaining a subtle sysfs superblock and NFS readahead failure, with a concrete fix. It is valuable but mainly to practitioners using EFS, containerd, and shared network namespaces.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.63total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.47
  • Reader interest0.73
  • Audience breadth0.44
  • Practical relevance0.69
  • Substantiated0.89
  • Technical depth0.96
  • New information0.91
  • Counts against: Promotional0.06
  • Counts against: Overclaim0.10

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.490.300.620.470.32+0.24+0.113
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.620.720.840.730.22+0.26+0.189
Audience breadthHow many people who build technology does it concern?0.480.400.430.440.08+0.13+0.057
Practical relevanceHow useful is it to someone who builds software or tech products?0.730.550.780.690.23+0.22+0.151
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.930.850.900.890.08+0.05+0.045
Technical depthHow technically substantive is it?1.000.920.950.960.08+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.890.900.940.910.05+0.05+0.046
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.050.050.080.060.03−0.19−0.011
OverclaimDo the headline or conclusions claim more than the body supports?0.150.100.060.100.09−0.11−0.011
Sum of contributions+0.625
Claim-check penalty0.000
Total, as published0.625

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #17 on Rubric, 10 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-10/17/"><img src="https://rubric.hrih.si/badge/2026-11-10/17.svg" alt="Ranked #17 on Rubric, 10 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 2 matches source · 2 no source given · 4 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkVersion

    Linux 5.4 reduced the default NFS readahead from 15 times rsize to 128 KiB.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Linux 5.4 dropped the default NFS readahead from 15 times rsize, which is 15 MiB with EFS's 1 MiB rsize, to 128 KiB”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/torvalds/linux/commit/c128e575514ce93dced349417d136304a33b6f99

  2. Matches sourceDate

    efs-utils has written 15 MiB readahead back at mount time since v1.30.2 in 2021.

    The cited source says the same thing.

    The article says

    “efs-utils has written 15 MiB back at mount time since v1.30.2 in 2021”

    The source says

    “To fix the issue, below function will modify read_ahead_kb to 15 * rsize (1MB by default) after mount”

    Source cited by the article: github.com/aws/efs-utils/commit/a07e4181e69b62a0f38d847f80d42a74bb70ac8d

  3. No source givenVersion

    efs-utils v3.3.2 lets its watchdog re-check the readahead value on every poll on any Linux 5.4 or later.

    The article gives no link or citation for it.

    The article says

    “v3.3.2 lets its watchdog re-check the value on every poll on any Linux 5.4 or later”

    The source says

    No source to compare with.

  4. Couldn’t checkVersion

    In Linux up to 5.3, NFS overrode the default BDI readahead with rsize times 15; since 5.4 it only sets io_pages and leaves the 128 KiB default.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “Up to 5.3, NFS overrode it with rsize times 15 (fs/nfs/super.c); since 5.4 it only sets io_pages and leaves the 128 KiB default”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/torvalds/linux/blob/v5.3/fs/nfs/super.c

  5. Couldn’t checkCausal conclusion

    sysfs keeps one superblock per network namespace, because it records the caller's network namespace as the mount's tag and reuses an existing superblock when root and tag match.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “sysfs keeps one superblock per network namespace. When sysfs is mounted, it records the caller's network namespace as the mount's tag”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/torvalds/linux/blob/v6.18/fs/sysfs/mount.c

  6. Matches sourceVersion

    containerd's default spec mounts /sys as sysfs with nosuid, noexec, nodev and ro, while WithPrivileged includes WithWriteableSysfs, which changes ro to rw.

    The cited source says the same thing.

    The article says

    “containerd's default spec mounts /sys as sysfs with nosuid, noexec, nodev and ro”

    The source says

    “Destination: "/sys", Type: "sysfs", Source: "sysfs", Options: []string{"nosuid", "noexec", "nodev", "ro”

    Source cited by the article: github.com/containerd/containerd/blob/v2.3.7/pkg/oci/mounts.go

  7. Couldn’t checkCausal conclusion

    mount -o remount,rw /sys reaches reconfigure_super(), which clears SB_RDONLY on the shared superblock without changing other containers' per-mount ro flags.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “clearing SB_RDONLY on the shared superblock”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/torvalds/linux/blob/v6.18/fs/super.c

  8. No source givenGeneralization

    Containers sharing a network namespace share one sysfs superblock, and the first to mount it picks ro or rw for all of them.

    The article gives no link or citation for it.

    The article says

    “Containers that share a network namespace share one sysfs superblock, and the first one to mount it picks ro or rw for all of them”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Remount sysfs to make its superblock rw: mount -O remount,rw /sys”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.