1

I have a shared Directory on my TeamCity Server, C:\Work which is about 9 GB and I want to move it to a separate Disk E:. When I copy the C:\Work to E:\Work and do mklink /D to make a symlink, the target folder is shared but the link does not appear to be shared. I simply want to delete C:\Work and create a symlink at C:\ that directs to E:\Work so that I may clear some space on the C:\ drive. It is important that the share still appears to be at C:\ since programs depend on it. What is the best practice here?

  • What is the best practice here? To not have applications depending on a share on someone's workstation. – HopelessN00b Mar 19 '13 at 17:45
  • 2
    It is not a workstation, it is a Windows Server dedicated application build server for the TeamCity application. The shared C:\build directory is a requirement of the build agent I believe. – user160910 Mar 19 '13 at 17:55
1

In this case I'd use a directory mounted volume. That would make C:\Work it's own volume, and not dependent upon the boot volume for providing space. It's more reliable than a symlink, and preserves the wince-worthy dependency you're working around.

  • OK, I am trying your suggestion. I renamed C:\Work to C:\Work_Original, I created a New Folder C:\Work and mounted E:\ to that folder. I then copied the contents of the original folder to the new mounted folder and set sharing and permissions to be what they were on the original folder. Does that seem like it should work and be transparent to programs looking for this folder? – user160910 Mar 19 '13 at 19:18
  • @GreggLeventhal That's exactly what I meant. It should Just Work. – sysadmin1138 Mar 19 '13 at 19:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy