From: Oskar Skog <novia@oskog97.com>
To: cygwin@cygwin.com
Subject: vboxsharedfs - Too many levels of symbolic links
Date: Tue, 30 Nov 2021 19:04:57 +0200 [thread overview]
Message-ID: <d6470ffe-8e49-3eb7-4d21-3212e0ad4f31@oskog97.com> (raw)
vboxsharedfs file systems no longer work. Any attempt to access will
result in "too many levels of symbolic links".
This only affects the VirtualBox shared folder, the Samba share works
just fine.
Last time I updated (before today) was sometime before the 10th of
September.
MSYS2 has the same problem, but no one seems to have reported it to
Cygwin:
https://github.com/msys2/msys2-runtime/issues/58
user@DESKTOP-******* ~$ ls /cygdrive/z
ls: cannot access '/cygdrive/z': Too many levels of symbolic links
user@DESKTOP-******* ~$ mount
C:/Cygwin/bin on /usr/bin type ntfs (binary,auto)
C:/Cygwin/lib on /usr/lib type ntfs (binary,auto)
C:/Cygwin on / type ntfs (binary,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
D: on /cygdrive/d type iso9660 (binary,posix=0,user,noumount,auto)
Y: on /cygdrive/y type smbfs (binary,posix=0,user,noumount,auto)
Z: on /cygdrive/z type vboxsharedfolderfs
(binary,posix=0,user,noumount,auto)
user@DESKTOP-******* ~$ uname -a
CYGWIN_NT-10.0 DESKTOP-* 3.3.2(0.341/5/3) 2021-11-08 16:55 x86_64 Cygwin
next reply other threads:[~2021-11-30 17:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 17:04 Oskar Skog [this message]
2021-11-30 21:40 ` Gackle, Philip P
2021-12-02 10:43 ` Corinna Vinschen
2021-12-05 2:54 ` Takashi Yano
2021-12-05 14:49 ` Oskar Skog
2021-12-06 3:31 ` Takashi Yano
2021-12-06 6:34 ` Oskar Skog
2021-12-06 8:04 ` Takashi Yano
2021-12-06 10:16 ` Corinna Vinschen
2021-12-06 10:55 ` Takashi Yano
2021-12-07 0:46 ` Takashi Yano
2021-12-07 14:57 ` Corinna Vinschen
2021-12-07 15:32 ` Takashi Yano
2021-12-07 15:43 ` Takashi Yano
2021-12-07 16:03 ` Corinna Vinschen
[not found] <Ya+WvmECA+zAbuV9@calimero.vinschen.de>
2021-12-08 8:20 ` Takashi Yano
2021-12-08 10:37 ` Corinna Vinschen
2021-12-09 8:16 ` Takashi Yano
2021-12-09 9:16 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6470ffe-8e49-3eb7-4d21-3212e0ad4f31@oskog97.com \
--to=novia@oskog97.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).