Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <428B0B51.CB8FB8A@dessent.net>
Date: Wed, 18 May 2005 02:30:57 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Mv after tar in a shell script problems
References: <md5:B6BCB6EDFB1BCC9CE4B7009818629D72>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

"Gary R. Van Sickle" wrote:

> ...and, if I change the mv to a loop which keeps trying if there's a
> failure:
> 
>   while ! mv dir_name_file.tar.bz2_untars_to new_dir_name; do echo "retrying
> move..."; done
> 
> it will eventually work after a few iterations.
> 
> I... huh?
> 
> I'll brew up a test case, this is nutso.

The only thing I can think of is that tar exits immediately after
issuing the final write() of the last file, and mv starts up before the
file system has a chance to finish commiting that write to disk.

The question would then be, does the filesystem allow close() to
complete even if there is still outstanding IO.  Maybe it has to do with
write caching of the drive.

Brian

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