Skip to content

Updates to wsl.conf no longer immediate #3994

Description

Please fill out the below information:

  • Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.18362.30]

  • What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

editing wsl.conf to add this automount section for mounting the C drive with metadata support:

[automount]
options = "metadata,umask=22,fmask=11"

exit and relaunch WSL for the drive to re-mount

  • What's wrong / what should be happening instead:

Drive is not remounted with new options. After an unknown period of time (~5 mins?) the change takes effect. This behaviour is seems new in windows 10 "1903". Previous build (1809 - something) the change would take effect immediately upon reload of wsl.

terminating wsl with new command wsl.exe --terminate Ubuntu causes the change to apply immediately

forcibly dismounting and re-mounting the volume with the same mount options works as well (though technicallly not reading the wsl.conf?)

cd ~
sudo umount /mnt/c
sudo mount -t drvfs C: /mnt/c -o metadata,uid=1000,gid=1000,umask=22,fmask=11
cd -

See our contributing instructions for assistance.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions