From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Bad Address with /cygdrive paths
Date: Wed, 21 Oct 2015 11:09:00 -0000 [thread overview]
Message-ID: <20151021110950.GP5319@calimero.vinschen.de> (raw)
In-Reply-To: <CAD-6W7bG+onWNhS31gRJ0YK589nLPpsnRo2RCth4JtOVPR6DHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
On Oct 12 18:59, Barry Roberts wrote:
> I've used cygwin for lots of years, and this is kind of weird to me.
> My operations guys set up some Windows Server 2012 R2 servers with
> Cygwin x86-64 2.2.1.
>
> There's a CIFS mount (from an HNAS) that I use a lot that is giving me
> problems. For example:
>
> $ ls /cygdrive/m/install
> ls: cannot access /cygdrive/m/install: Bad address
Would you mind to run strace in this scenario:
$ strace -o ls.trace ls /cygdrive/m/install
and attach the ls.trace file here?
>
> But:
> $ ls m:/install
>
> Works just great.
>
> Using /cygdrive/m I can list the contents of the root of the drive,
> but I can't read any files. And any subdirectory just gives me the
> "Bad address" error. Everything (except completion) works just fine
> with m:/ paths.
>
> This isn't a huge deal. I mostly use cygwin on these servers to
> manage them with scripts, so I've changed my configuration variables
> to <drive letter>: paths and everything seems to work. But I did
> spend nearly half a day figuring this out, so I'm curious if there's a
> configuration problem or a known issue that my searches haven't
> uncovered yet.
Nothing I'd be aware of.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-21 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 0:59 Barry Roberts
2015-10-21 11:09 ` Corinna Vinschen [this message]
2015-10-21 14:44 ` Barry Roberts
2015-10-21 14:49 ` Barry Roberts
2015-10-21 16:41 ` Corinna Vinschen
2015-10-22 16:21 ` Corinna Vinschen
2015-10-22 16:34 ` Barry Roberts
2015-10-22 17:31 ` Barry Roberts
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=20151021110950.GP5319@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).