3 ms·

The filesystem integration is not without flaws though, it doesn't seem to implement full posix semantics. Many times in WSL2 I've had a git rebase fail becaus

by tremon 6y ago

The filesystem integration is not without flaws though, it doesn't seem to implement full posix semantics. Many times in WSL2 I've had a git rebase fail because it couldn't overwrite existing files, and every time it could be fixed by just running git rebase --continue. The actual problem seems to be that WSL2 system calls return before the NTFS operation completes, so quick successions of create-after-unlink or write-after-rename can have unexpected results. For this reason I still keep a WSL1 environment, it doesn't have the same issues (and doesn't appear to be any slower for filesystem operations).

Filligree 6y ago
> For this reason I still keep a WSL1 environment, it doesn't have the same issues (and doesn't appear to be any slower for filesystem operations). It's definitely a great deal slower for filesystem operations inside the Linux system. Filesystem operations outside the VM's disk image go through 9p, which gives you basically the same performance for both.