X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Subject:	RE: "tar --one-file-system" accesses remote file systems
Date:	Wed, 13 Feb 2008 12:03:58 -0800
Message-ID:	<70952A932255A2489522275A628B97C30620E123@xmb-sjc-233.amer.cisco.com>
In-Reply-To:	<47B3413C.4040007@cygwin.com>
References:	<47B3413C DOT 4040007 AT cygwin DOT com>
From:	"Matt Seitz (matseitz)" <matseitz AT cisco DOT com>
To:	<cygwin AT cygwin DOT com>
Authentication-Results:	sj-dkim-3; header.From=matseitz AT cisco DOT com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
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
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id m1DK43lS020534

> From: Larry Hall (Cygwin) 
> 
> Matt Seitz (matseitz) wrote:
> > 
> >> Matt Seitz (matseitz) wrote:
> >>> This problem and a proposed solution was mentioned in an earlier 
> >>> e'mail 
> (http://www.cygwin.com/ml/cygwin/1998-09/msg00839.html). 
> > 
> > Ah, yes, the mounted CIFS share is reported as a FAT file 
> > system*. 
> 
> That's it I expect.  Going straight to the code, in 
> fhandler_disk_file.cc, here's some code from 
> fhandler_base::fstat_helper():
> 
>    /* Enforce namehash as inode number on untrusted file systems. */
>    if (pc.isgood_inode (nFileIndex))
>      buf->st_ino = (__ino64_t) nFileIndex;
>    else
>      buf->st_ino = get_namehash ();
> 
> One of the things that isgood_inode() checks for is that it's 
> not a FAT drive.  In case it is, you end up with a faked hash inode.

Thanks for the diagnosis.  I'm curious about something.  The message I reference above also mentioned an issue with "st_dev".  It seems to imply that correcting the "st_dev" to use the volume serial number could resolve this issue.  What is your opinion on that theory? 


--
Matt Seitz
Manager, File System Virtualization
Cisco Systems, Inc.
.:|:.:|:.  

- Raw text -