search for: prev_dirpos

Jeremy, I think we found the part of source where the problem resides: smbd/trans2.c +1444 for (i=0;(i<maxentries) && !finished && !out_of_space;i++) { +1445 BOOL got_exact_match = False; +1446 +1447 /* this is a heuristic to avoid seeking the dirptr except when +1448 absolutely necessary. It allows for

Over the weekend I upgraded my IRIX servers to 3.0.13 and have found many strange issues regarding the creation of new folders. When I attempt to add a new folder through the Windows side I get an immediate error dialog box stating "You may not be able to access file created in the folder X:\New Folder." When I select to continue the folder is created, looking on the IRIX side the

...No worries, we saved off the 'offset = telldir()' before doing the readdir that returned filename "m". So we seek back to the offset before the filename "m" in this code: if (NT_STATUS_EQUAL(status, STATUS_MORE_ENTRIES)) { dptr_SeekDir(dirptr, prev_dirpos); return status; } and return the findfirst reply with files a-l. Now when the listing continues, it'll do so with filename "m" etc. until the listing is done. If: offset = telldir() seekdir(offset) doesn't return us to the same position in the direc...

I'm trying to get to the bottom of where the normal directory functions differ in results for block storage compared to NFS. I created a short c script to look at the offsets generated for the directory when block storage backed in comparison to NFS backed. block storage backed are always positive: File: 5050, Offset: 9213006461214587617 File: 6567, Offset: 9218690536865144001 File: 4033,