From: Eliot Moss <moss@cs.umass.edu>
To: cygwin <cygwin@cygwin.com>
Subject: Anyone tried to use restic to backup a Cygwin install?
Date: Fri, 31 Dec 2021 11:24:33 -0500 [thread overview]
Message-ID: <b6a5e6da-bcef-35cd-364f-fc3205de159f@cs.umass.edu> (raw)
Dear Cygwiners - Has anyone else out there tried to use a Windows build of
restic to backup a volume that includes a Cygwin installation? I get a lot of
errors like this one:
error: open \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7\cygwin64\bin\2to3: The file cannot be
accessed by the system.
That file is some kind of symlink to /etc/alternatives/2to3. Of course, using
that path, a Windows program won't find the target, but it should be able to
just backup the link contents.
Using Windows Explorer, I tried to open the file with Notepad, and I get the
same message.
I have winsymlinks:native set in my CYGWIN env variable, though I can't say
whether that setting ws used to create this particular link and its friends.
In CMD, DIR /AL /S on C:\cygwin64\bin lists these links as <JUNCTION>.
Windows Explorer Properties does not show Link Properties.
My question boils down to this, I believe, in terms of how to resolve this:
- Should I change the links in Cygwin? If so, to what kind? (Note: something
similar happens with a bunch of links in my WSL install of Ubuntu, and I
probably can't just change the junctions there.)
- Should I report this as an issue to the restic people, about the handling of
junctions? (Actually, I will file an issue anyway, but wonder if anyone has
advice / info to offer.)
Regards, and Happy New Year, everyone! Eliot Moss
reply other threads:[~2021-12-31 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b6a5e6da-bcef-35cd-364f-fc3205de159f@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).