Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <42C2FE58.BCC2F895@dessent.net> Date: Wed, 29 Jun 2005 13:02:32 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: tar 1.13.25: extracts of files using hardlinks w/i same win32 directory lost References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.9/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin@cygwin.com rkoroly@memphis.edu wrote: > When I tar xvf tarfile.tar into a NTFS, Win Server 2003, directory all > files that define hardlinks within the same directory name are lost. If > the hardlink is located in another directory, the links appears to work. > When watching the extraction, the files appear to be extracted but when > the linking file is extracted a missing link message is displayed and > the original file is deleted. The example that I have is that a > directory of runtime objects needs to be described in upper and lower > case. This is accomplished thru hardlinks. After the extract completes > no files exists because each linked file deleted its associated file. WJFFM: $ touch a $ ln a b $ ls -li total 0 3096224743819983 -rw-r--r-- 2 brian None 0 Jun 29 12:55 a 3096224743819983 -rw-r--r-- 2 brian None 0 Jun 29 12:55 b $ tar c a b | (mkdir testdir; cd testdir; tar x; ls -li) total 0 1688849860266705 -rw-r--r-- 2 brian None 0 Jun 29 12:55 a 1688849860266705 -rw-r--r-- 2 brian None 0 Jun 29 12:55 b Tar recreated the hard links to the files in the same directory upon extraction. I think you will have to elaborate on this 'different filenames with same case' thing because that is not supported under Windows, which is likely your actual problem, not tar. Windows file systems preserve case but are not case sensitive, so you cannot have two files with the same filename but different cases. That is a design limitation and there's nothing tar can do to get around it. You can however try a managed mount. 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/