starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

can't see file whitch create by explorer.exe using 'ls' in wsl bash #39

New Issue
Closed
opened 2026-01-30 21:40:21 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 21:40:21 +00:00
Owner
Copy Link

Originally created by @wengzuyang on GitHub (Dec 24, 2017).

  • Your Windows build number: Microsoft Windows [Version 10.0.16299.125]

  • What you're doing and what's happening:
    Using explorer.exe create a new file to "C:\Users\Administrator\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs/opt"，then using bash to 'ls' it .
    image

  • What's wrong / what should be happening instead: can't see this file in bash.
    image

Originally created by @wengzuyang on GitHub (Dec 24, 2017). * Your Windows build number: Microsoft Windows [Version 10.0.16299.125] * What you're doing and what's happening: Using explorer.exe create a new file to "C:\Users\Administrator\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs/opt"，then using bash to 'ls' it . ![image](https://user-images.githubusercontent.com/11473283/34324068-21755e4a-e89e-11e7-8a82-e0e88595d392.png) * What's wrong / what should be happening instead: can't see this file in bash. ![image](https://user-images.githubusercontent.com/11473283/34324070-55ebbda4-e89e-11e7-9132-1df583f70072.png)
claunia added the Issue-QuestionProduct-WSL labels 2026-01-30 21:40:21 +00:00
claunia commented 2026-01-30 21:40:22 +00:00
Author
Owner
Copy Link

@khouzam commented on GitHub (Dec 24, 2017):

Hi @wengzuyang

This isn't really an issue with the console but with WSL and is by design as described in this blog post on how the WSL filesystem works. The following paragraph explains the problem.

Interoperability with Windows

While VolFs files are stored in regular files on Windows in the directories mentioned above, interoperability with Windows is not supported. If a new file is added to one of these directories from Windows, it lacks the EAs needed by VolFs, so VolFs doesn’t know what to do with the file and simply ignores it. Many editors will also strip the EAs when saving an existing file, again making the file unusable in WSL.

Additionally, since VFS caches directory entries, any modifications to those directories that are made from Windows while WSL is running may not be accurately reflected.

@khouzam commented on GitHub (Dec 24, 2017): Hi @wengzuyang This isn't really an issue with the console but with WSL and is by design as described in [this blog post](https://blogs.msdn.microsoft.com/wsl/2016/06/15/wsl-file-system-support/) on how the WSL filesystem works. The following paragraph explains the problem. Interoperability with Windows While VolFs files are stored in regular files on Windows in the directories mentioned above, interoperability with Windows is not supported. If a new file is added to one of these directories from Windows, it lacks the EAs needed by VolFs, so VolFs doesn’t know what to do with the file and simply ignores it. Many editors will also strip the EAs when saving an existing file, again making the file unusable in WSL. Additionally, since VFS caches directory entries, any modifications to those directories that are made from Windows while WSL is running may not be accurately reflected.
claunia commented 2026-01-30 21:40:22 +00:00
Author
Owner
Copy Link

@wengzuyang commented on GitHub (Dec 26, 2017):

It explains the matter,thanks.

@wengzuyang commented on GitHub (Dec 26, 2017): It explains the matter,thanks.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Product-WSL
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#39
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?