MOUNT.EROFS(8)

πŸ“¦ version 1.9.4, in alpine 3.24, arch rolling, fedora 43, fedora 44, nixos 26.05

πŸ’– MOUNT.EROFS β€” the manual page, but make it slay πŸ’–

okay bestie, sit down, hydrate, because we're about to talk about mount.erofs, a System Manager's Manual entry, section 8. she's part of erofs-utils and she's lowkey the most put-together tool in the whole friend group. πŸŽ€


✨ NAME ✨

mount.erofs β€” manage EROFS filesystem


🌸 SYNOPSIS 🌸

mount.erofs [OPTIONS] SOURCE MOUNTPOINT
mount.erofs -u TARGET
mount.erofs --reattach TARGET

πŸ¦‹ DESCRIPTION πŸ¦‹

So. EROFS is an enhanced lightweight read-only filesystem with modern designs for scenarios that need high-performance read-only requirements. she's the girl who shows up, does the job, and doesn't need a whole personality crisis about it. πŸ’…

mount.erofs is what you use to mount an EROFS filesystem from SOURCE (which can be an image file or a block device, she doesn't judge) onto a MOUNTPOINT. and the way that she supports multiple backends?? direct kernel mount, FUSE-based mount, and NBD (Network Block Device) for remote sources like OCI images. versatility, periodt. ✨


πŸ‘‘ OPTIONS πŸ‘‘

  • -h, --help β€” display help message and exit. bestie just tells you what's up.
  • -V, --version β€” display version information and exit. her little introduction moment.
  • -o options β€” comma-separated list of mount options. see MOUNT OPTIONS below, i gotchu. πŸ’–
  • -t type[.subtype] β€” specify the filesystem type and optional subtype. the type should be erofs. available subtypes are:
    • fuse β€” use FUSE-based mount via erofsfuse.
    • local β€” force direct kernel mount (default if available).
    • nbd β€” use NBD backend for remote sources (e.g., OCI images).
  • -u β€” unmount the filesystem at the specified target.
  • --reattach β€” reattach to an existing NBD device and restart the NBD service.

🌈 MOUNT OPTIONS 🌈

Standard mount options, the classics, the icons:

  • ro β€” mount the filesystem read-only (default).
  • rw β€” mount the filesystem read-write (not supported for EROFS).
  • nosuid β€” do not honor set-user-ID and set-group-ID bits.
  • suid β€” honor set-user-ID and set-group-ID bits (default).
  • nodev β€” do not interpret character or block special devices.
  • dev β€” interpret character or block special devices (default).
  • noexec β€” do not allow direct execution of any binaries.
  • exec β€” allow execution of binaries (default).
  • noatime β€” do not update inode access times.
  • atime β€” update inode access times (default).
  • nodiratime β€” do not update directory inode access times.
  • diratime β€” update directory inode access times (default).
  • relatime β€” update inode access times relative to modify or change time.
  • norelatime β€” do not use relative atime updates.

πŸ“ OCI-SPECIFIC OPTIONS πŸ“

the following OCI-specific options are available (yes queen, containers too):

  • oci.blob=digest β€” specify the OCI blob digest to mount. the digest should be in the format sha256:..... cannot be used together with oci.layer. pick a lane bestie πŸ’€
  • oci.layer=index β€” specify the OCI layer index to mount (0-based). cannot be used together with oci.blob. same energy, opposite direction.
  • oci.platform=platform β€” specify the target platform (default: linux/amd64).
  • oci.username=username β€” username for OCI registry authentication.
  • oci.password=password β€” password for OCI registry authentication.
  • oci.tarindex=path β€” path to a tarball index file for hybrid tar+OCI mode.
  • oci.zinfo=path β€” path to a gzip zinfo file for random access to gzip-compressed tar layers.
  • oci.insecure β€” use HTTP instead of HTTPS to access the image registry. πŸ™ˆ

πŸ’œ NOTES πŸ’œ

  • EROFS filesystems are read-only by nature. the rw option will be ignored. she said no and she meant it. 🫢
  • When mounting OCI images via NBD, the mount process creates a background daemon to serve the NBD device. the daemon will automatically clean up when the filesystem is unmounted. self-sufficient queen, no notes. πŸ‘‘
  • The --reattach option is useful for recovering NBD mounts after a system crash or when the NBD daemon was terminated unexpectedly. she's giving resilience, she's giving comeback era. ✨
  • Kernel direct mount is used when mounting a regular file without specifying a backend type. if file-based mounts is unsupported, loop devices will be set up automatically.
fr fr, read these notes before you come crying to the group chat. 😭

🧚 SEE ALSO 🧚

mkfs.erofs(1), erofsfuse(1), dump.erofs(1), fsck.erofs(1), mount(8), umount(8)


⭐ AVAILABILITY ⭐

mount.erofs is part of erofs-utils.


and that's the whole page, bestie!! πŸ’– mount.erofs, section 8 of the System Manager's Manual, shipped as part of erofs-utils β€” go mount something read-only and be iconic about it. πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from