X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="UTF-8"
Subject: Re: "tar --one-file-system" accesses remote file systems
Date: Wed, 13 Feb 2008 10:29:39 -0800
Message-ID: <70952A932255A2489522275A628B97C30620E047@xmb-sjc-233.amer.cisco.com>
From: "Matt Seitz (matseitz)" <matseitz AT cisco DOT com>
To: <cygwin AT cygwin DOT com>
Authentication-Results: sj-dkim-4; header.From=matseitz AT cisco DOT com; dkim=pass ( 	sig from cisco.com/sjdkim4002 verified; );
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id m1DJVRpT014766



"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com> wrote in message news:<47B31A8F DOT 7060008 AT cygwin DOT com>...
> 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). Is
> > there a known solution to this issue?
> 
> You can check recent (and not so recent) email archives on the subject.  

I tried.  The only discussion I found was the link above.  If you can give me a pointer to another thread, I'd appreciate it.  I'll also try additional searches based on the information you gave below.

> As
> I recall, it depends on your server and it's version.  Older versions or FAT
> file-systems have their inodes "faked".  This may be the cause of the
> problem you're seeing.

Ah, yes, the mounted CIFS share is reported as a FAT file system*.  So that may be the problem.  I'll try it with a Windows server sharing an NTFS volume and see if I get a different result.  

*It's actually a Network Appliance ONtap WAFL QTree, configured to use "UNIX" security model.  But ONtap reports "UNIX" QTrees as "FAT" file systems to CIFS clients.