Re:DTrace on Windows
by otterley on Monday March 11, 2019 @02:45PM
(#19361631)
That error is orthogonal to the filesystem in use. Every OS that provides exclusive locking, regardless of filesystem, will return an error if more than one process wants to acquire such a lock.
[ Parent
| on HN ]
PS> $lockedFile="C:\Windows\System32\wshtcpip.dll"
PS> Get-Process | foreach{$processVar = $_;$_.Modules | foreach{if($_.FileName -eq $lockedFile){$processVar.Name + " PID:" + $processVar.id}}}
Re:DTrace on Windows
by jodrellblank on Monday March 11, 2019 @08:18PM
(#19364209)
PS C:\> gps |? {$_.Modules.FileName -match "wshtcpip\.dll"} | select name, id
Re:DTrace on Windows
by felixfbecker on Monday March 11, 2019 @06:04PM
(#19363322)
That foreach looks like it should really be a where
It was copied from stackoverflow... apologies, I just knew it was possible.
Re:DTrace on Windows
by reitanqild on Monday March 11, 2019 @03:36PM
(#19362062)
> Every OS that provides exclusive locking, regardless of filesystem, will return an error if more than one process wants to acquire such a lock.
Obviously.
The super annoying thing is when the OS doesn't try to tell you which process(es) keeps it open and doesn't even ship with built in tooling to let you find out on your own.
I think that is the point GP tries to make.
Re:DTrace on Windows
by Negitivefrags on Monday March 11, 2019 @04:01PM
(#19362243)
Open up "Resource Monitor" and go to the "Disk" tab. Under "Disk Activity" you can see all open file handles.
Re:DTrace on Windows
by kevin_thibedeau on Monday March 11, 2019 @06:10PM
(#19363369)
Certainly not a sensible solution like having a dialog button that gives you all the relevant information immediately and empowers you to solve the problem without a goose chase.
Which are thousands...
You need the Sysinternals utilities to make life tolerable: https://docs.microsoft.com/en-us/sysinternals/downloads/hand... from the command line or Ctrl-F in https://docs.microsoft.com/en-us/sysinternals/downloads/proc... if you prefer a GUI. They do a brute-force search over the open handles in all processes, but it's effective.
Re:DTrace on Windows
by noisem4ker on Tuesday March 12, 2019 @08:30PM
(#19374526)
I prefer this utility: http://www.emptyloop.com/unlocker/
It lets you see which process locked a file, and optionally remove the lock.