In both 3.5.16 and 3.6.8, during our testing, we found that the archive flag is always set on directories. We noticed this behavior, however, have not yet found bad effect on file access because of that. However would like to see if this can be fixed. It seems that Samba defaults map archive to yes. sfcstlx0102_01:~ # testparm -s -v | grep archive Load smb config files from /opt/samba3518/lib/smb.conf Unknown parameter encountered: "realm" Ignoring unknown parameter "realm" Processing section "[cifsshare]" Processing section "[onefs]" Loaded services file OK. Server role: ROLE_STANDALONE map archive = Yes sfcstlx0102_01:~ #
More complete explanation of the bug. Creating a directory to a Samba share sets the attributes to 'D' only. However then doing a rename of that directory sets the 'A' attribute in error (as is done on a file rename). Fix to follow, including new test code to ensure we don't regress. Jeremy.
Created attachment 8478 [details] git-am fix for master and 4.0.x Fix + regression test. Jeremy.
Created attachment 8479 [details] git-am fix for 3.6.x.
Comment on attachment 8479 [details] git-am fix for 3.6.x. Fix only for 3.6.x, regression test in 4.0.x patch only.
Comment on attachment 8478 [details] git-am fix for master and 4.0.x In master as 3d46a077dd0999cc0c6032379147811c8bb660fb and d79485a566e3c59ce53c3ee205aa6c78f149f5d8.
Re-assigning to Karolin for inclusion in 4.0.next and 3.6.next. Jeremy.
Pushed to v3-6-test and autobuild-v4-0-test.
Pushed to v4-0-test. Closing out bug report. Thanks!