This is the mail archive of the
mailing list for the Cygwin project.
RE: "tar --one-file-system" accesses remote file systems
- From: "Matt Seitz (matseitz)" <matseitz at cisco dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 13 Feb 2008 12:03:58 -0800
- Subject: RE: "tar --one-file-system" accesses remote file systems
- Authentication-results: sj-dkim-3; header.Fromemail@example.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
- References: <47B3413C.firstname.lastname@example.org>
> 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
> > 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
> /* Enforce namehash as inode number on untrusted file systems. */
> if (pc.isgood_inode (nFileIndex))
> buf->st_ino = (__ino64_t) nFileIndex;
> 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?
Manager, File System Virtualization
Cisco Systems, Inc.