Cannot access volumes mounted with 'mklink /d' which point to a volume UUID
Corinna Vinschen
corinna-cygwin@cygwin.com
Thu Feb 16 09:26:00 GMT 2017
On Feb 15 07:30, Matt D. wrote:
> On Windows you can create symbolic links which point to volume UUIDs as a
> way of mounting and unmounting them without having to use the administrative
> disk management tools.
>
> For example, in cmd:
>
> mountvol
> ...
> \\?\Volume{079b79c9-0000-0000-0000-100000000000}\
> C:\
> ...
> mklink /d test \\?\Volume{079b79c9-0000-0000-0000-100000000000}\
> ...
> dir test
>
> I call mounvol to get a list of volumes and create a symbolic link 'test'
> which points to the C:\ UUID. When I then 'dir test' it will list all files
> on that volume.
>
> If I try to access it through Cygwin Bash I get the following error:
>
> $ dir test/
> dir: cannot access 'test/': No such file or directory
>
> This makes it difficult to work with unmounted volumes as it's not always
> possible to access the administrative disk management snap-in and the
> mountvol/mklink has always been my go-to for this type of functionality. It
> would be great if Cygwin would support it.
This type of directory symlink to a GUID volume path isn't supported
at all yet in Cygwin. However, you can access the directory directly
without having to go through MKLINK. In Cygwin:
$ cd /proc/sys/GLOBAL\?\?/Volume{079b79c9-0000-0000-0000-100000000000}/
or
$ ln -s \
/proc/sys/GLOBAL\?\?/Volume\{079b79c9-0000-0000-0000-100000000000}/ \
my_vol
$ cd my_vol
Note the trailing slash. Volume{079b79c9-0000-0000-0000-100000000000}
without the slash is the block device.
Volume{079b79c9-0000-0000-0000-100000000000}/ with trailing slash is the
filesystem on the block device.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20170216/515b1f59/attachment.sig>
More information about the Cygwin
mailing list