X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Fri, 21 Dec 2012 18:19:16 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: trouble accessing samba shares with spaces and/or parentheses
Message-ID: <20121221171916.GH18188@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <50D48C53.2080403@mailme.ath.cx> <20121221164750.GE18188@calimero.vinschen.de> <50D495D5.2030104@mailme.ath.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <50D495D5.2030104@mailme.ath.cx>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Dec 21 18:01, bartels wrote:
> On 12/21/2012 05:47 PM, Corinna Vinschen wrote:
> >On Dec 21 17:20, bartels wrote:
> >>$ net use Q: "$(cygpath -w '//macau/X32 Backup-4(WD)')" "bartels" /user:"bartels"
> >>The command completed successfully.
> >>
> >>$ ls q:/
> >>ls: cannot access q:/: Input/output error
> >Please don't use DOS paths.  Use POSIX paths like /cygdrive/q instead:
> >http://cygwin.com/cygwin-ug-net/using.html#pathnames-win32
> 
> Naturally, I tried all flavours:
> 
> $ ls /cygdrive/q/
> ls: cannot access /cygdrive/q/: Input/output error
> 
> 
> 
> >Works fine for me using a Linux Samba share with space in it.
> 
> Okay, that leaves the parentheses as the likely troublemaker.
> The thing is, people bring in disks, and I have no control over their volume / share names.
> 
> Any more ideas? Where's Santa when you need him ;-)

"Input/output error" is just an EIO.  strace might show more useful
information.  EIO could be generated for a couple of reasons, for
instance, the WIn32 errors ERROR_DISK_CORRUPT or ERROR_OPEN_FAILED are
translated to the POSIX EIO.  Another chance to get EIO is if something
goes badly wrong trying to read a symlink.  Or, that's always a chance,
the OSX smb server doesn't support some system call used by Cygwin.  It
wouldn't be the first such FS.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

