Page 1 of 1

Hardlink Error: process in use

Posted: Fri May 23, 2014 9:38 pm
by therube
Hardlink Error: "process in use"
(Actually, "The process cannot access the file because it is being used by another process.")

Note the "dctmp__".

I had a group with 66 dups.
Select all in the group, then specifically deselected the old & newest, leaving 64 marked.
Have always been leery of Hard Links (in Windows), but rather then outright deletion, figured I'd give it a shot.

Ah! It was me!
I had two of those files "open" in my file comparison program.

So when DC tried to set the links, it said, whoops, "in use".
And what it did, was to actually create the set of linked files, but named as "dctmp__stglyear.ARJ" rather then stglyear.ARJ.

Easy enough to deal with, but maybe there's some way to catch a situation like that?

(Sample:)

Code: Select all

Hardlink Error: C:\BIN\TAR\OLD\2009-0109\dctmp__stglyear.ARJ Locked: The process cannot access the file because it is being used by another process.
Hardlink Error: C:\BIN\TAR\OLD\2009-0325\dctmp__stglyear.ARJ Locked: The process cannot access the file because it is being used by another process.
Hardlink Error: C:\BIN\TAR\OLD\2009-0528\dctmp__stglyear.ARJ Locked: The process cannot access the file because it is being used by another process.
Hardlink Error: C:\BIN\TAR\OLD\2009-0704\dctmp__stglyear.ARJ Locked: The process cannot access the file because it is being used by another process.
Hardlink Error: C:\BIN\TAR\OLD\2009-0902\dctmp__stglyear.ARJ Locked: The process cannot access the file because it is being used by another process.

Re: Hardlink Error: process in use

Posted: Tue May 27, 2014 6:57 pm
by therube
(after that, I stopped working working it, figuring i'd return at a later time...)

Now I see what it actually did.
All the original files, stglyear.ARJ were left, unchanged (& un-linked).
All the dctmp__stglyear.ARJ were newly created (as links).

(so off to delete the dctmp__stglyear.ARJ files & try again...)

Successful :-).

Re: Hardlink Error: process in use

Posted: Mon Jun 02, 2014 2:13 pm
by DigitalVolcano
Looks like there is a bug with cleaning up the temporary hardlink files when there is a lock on the file - it should just fail with no temporary file created as a don't think you can hardlink a locked file.

I've logged the bug!