-
Notifications
You must be signed in to change notification settings - Fork 814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deleted files with open file handles don't behave correctly in drvfs #1807
Comments
Hi @clockfort -- thanks for the detailed write-up! I think this is the same underlying issue as #1535 , though a somewhat different scenario. In short, it's a clash between Windows and Linux semantics. Windows doesn't allow you to remove an open file. Linux does. DrvFs must support both simultaneously. Since the two have conflicting requirements, there must necessarily be rough edges; the question is where the WSL team chooses to put them. Related to that point: Do you have a program or script that depends on the Linux behavior? Or is this just a curiosity that you observed? When trade-offs need to be mande, the WSL team often seems to prefer to make trade-offs in favor of what's most useful to the most people. |
Yeah, I know why there'd be rough edges around this :-) My situation specifically was that I had a git directory, and checking out another branch deleted and added files to directory; including a file that a gradle daemon had an open handle on; the checkout threw an error because it couldn't put back a (different version) of the file in the same place.
|
Yeah, certainly possible. |
I believe @JasonLinMS fixed this recently. |
Duplicate of #966. |
A brief description
A deleted file with open file handles on it does not behave correctly on drvfs; it is still semi-visible to some applications when accessed via directory listing. (I have repro'd the issue in
ls
andgit
)Actual results / repro steps
Build 15048
The text was updated successfully, but these errors were encountered: