Is there any functional difference between creating a junction point on the Drivepool drive letter itself, vs. placing it on the physical disk directly?
I don't like that their placement does not follow file placement rules, and I don't trust junction points existing on removable disks in case they fail to connect on a reboot.
For instance,
mklink /j E:\Downloads D:\Downloads (Where E:\ is Drivepool)
vs
mklink /j C:\drivepool\phsyicaldiskone\poolpart.6sdas68x4a65s4d6a\Downloads D:\Downloads (Where C:\Drivepool\Physicaldiskone is... physical disk one)
I'm not trying to blow stuff up, but if it's all the same I'd like to dictate where the junction points get physically created.
Question
fattipants2016
Is there any functional difference between creating a junction point on the Drivepool drive letter itself, vs. placing it on the physical disk directly?
I don't like that their placement does not follow file placement rules, and I don't trust junction points existing on removable disks in case they fail to connect on a reboot.
For instance,
mklink /j E:\Downloads D:\Downloads (Where E:\ is Drivepool)
vs
mklink /j C:\drivepool\phsyicaldiskone\poolpart.6sdas68x4a65s4d6a\Downloads D:\Downloads (Where C:\Drivepool\Physicaldiskone is... physical disk one)
I'm not trying to blow stuff up, but if it's all the same I'd like to dictate where the junction points get physically created.
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.