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/