www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
Date: | Tue, 12 Jan 2010 16:14:27 +0100 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: 'as it was replaced while being copied' |
Message-ID: | <20100112151427.GB25477@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <1263308651 DOT 20352 DOT 1354240663 AT webmail DOT messagingengine DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <1263308651.20352.1354240663@webmail.messagingengine.com> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Jan 12 10:04, Charles Wilson wrote: > $ cp ../*cpp . > cp: skipping file `../tactical_transmit_msg.cpp', as it was replaced > while being copied > cp: skipping file `../test.cpp', as it was replaced while being copied > cp: skipping file `../test2.cpp', as it was replaced while being copied > cp: skipping file `../xml_message_types.cpp', as it was replaced while > being copied > > This is on a SMB share (actually, it's a distributed file system exposed > to windows via SMB). I've attached the output of cygcheck and > getvolinfo. > > This is the first time I've tried to do anything on this share since > upgrading to 1.7.1-official, but before the holidays I was using > 1.7.0-nn, on a 32bit machine. For Christmas IT gave me a brand new 64 > bit machine, and they may (or may not) have changed something with > regards to this filesystem over the holidays -- so the "culprit" is not > necessarily something that changed *in cygwin*. But I'd still like cp to > work... > > Any ideas? Debugging might help. Is that SMB as in Samba or as in real remote NTFS? The error message points to an unreliable inode handling. 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |