X-Spam-Check-By: sourceware.org Date: Fri, 14 Apr 2006 11:08:36 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Spam:Re: Find not working w/ Samba drive Message-ID: <20060414090836.GM9135@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <443BA3CA DOT 6070208 AT byu DOT net> <2919 DOT 71 DOT 113 DOT 94 DOT 37 DOT 1144784474 DOT squirrel AT wm0> <443C0749 DOT 6000106 AT maplesoft DOT com> <20060412094839 DOT GA10758 AT calimero DOT vinschen DOT de> <20060412153937 DOT GF9135 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Apr 13 11:01, Shankar Unni wrote: > Corinna Vinschen wrote: > > >Btw., I have hacked together a tiny testcase which lists a directory and > >evaluates the inode numbers using readdir and lstat. I would be > >interested to see the output for some smaller directories on shares > >using pre-3.0 Samba versions. > > This is the output from a server running > > "Version Samba for GuardianOS v2.6.050.200310180953" > > (this is a Snap Appliance file server, which seems to be a 2.4.19 linux > kernel. Not sure if they've tweaked smbd in any way..): > > % ./st //hq-share1 > Documents d: 000000000000000000, st: 018014724927011328 > Backup d: 000000000000000000, st: 1495201458608421376 > Builds d: 000000000000000000, st: 1297557616381147648 > . d: 000000000000000000, st: 3313024975094127606 > .. d: 000000000000000000, st: 000000000006035200 > > % % ./st //hq-share1/Backup (names obfuscated..) > . d: 000000000000000000, st: 1495201458608421376 > .. d: 000000000000000000, st: 3313024975094127606 > xxxx1 d: 000000000000000000, st: 1531250493513284096 Sorry, no, that's impossible. If the file system returns 0 for d_ino, or the file system is treated as unreliable, the Cygwin snapshots will always fake a non-0 inode number in d_ino. It looks like you're using a non-matching 'struct dirent' definition. Did you build the executable using the dirent.h file from the snapshot? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/