On Tue, Mar 12, 2013 at 7:55 AM, Wolfgang Stengel < wolfgang.sten...@efactory.de> wrote:
> Hello list, > > since a couple of weeks commits from a Windows system in a Samba shared WC > take much longer than before (using Windows 7, Subversion client 1.7.8). > > I tracked this down to Subversion accessing .svn/wc.db-journal and > .svn/wc.db-wal over and over again (thousands of times). Both files do not > exist in the WC. It looks like this in the Samba log: > > [2013/03/12 12:47:19.260464, 3] smbd/process.c:1662(process_smb) > Transaction 719619 of length 150 (0 toread) > [2013/03/12 12:47:19.260507, 3] smbd/process.c:1467(switch_message) > switch message SMBtrans2 (pid 28855) conn 0x7fab8064b800 > [2013/03/12 12:47:19.260542, 3] > smbd/trans2.c:5117(call_trans2qfilepathinfo) > call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 > [2013/03/12 12:47:19.260608, 3] smbd/vfs.c:905(check_reduced_name) > check_reduced_name [epson_neon_test/.svn/wc.db-journal] > [/home/wwwdocs/svn/wolfgang] > [2013/03/12 12:47:19.260663, 3] smbd/vfs.c:1039(check_reduced_name) > check_reduced_name: epson_neon_test/.svn/wc.db-journal reduced to > /home/wwwdocs/svn/wolfgang/epson_neon_test/.svn/wc.db-journal > [2013/03/12 12:47:19.260733, 3] > smbd/trans2.c:5236(call_trans2qfilepathinfo) > call_trans2qfilepathinfo: SMB_VFS_STAT of > epson_neon_test/.svn/wc.db-journal failed (No such file or directory) > [2013/03/12 12:47:19.260777, 3] smbd/error.c:81(error_packet_set) > error packet at smbd/trans2.c(5238) cmd=50 (SMBtrans2) > NT_STATUS_OBJECT_NAME_NOT_FOUND > [2013/03/12 12:47:19.261117, 3] smbd/process.c:1662(process_smb) > Transaction 719620 of length 142 (0 toread) > [2013/03/12 12:47:19.261160, 3] smbd/process.c:1467(switch_message) > switch message SMBtrans2 (pid 28855) conn 0x7fab8064b800 > [2013/03/12 12:47:19.261195, 3] > smbd/trans2.c:5117(call_trans2qfilepathinfo) > call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 > [2013/03/12 12:47:19.261260, 3] smbd/vfs.c:905(check_reduced_name) > check_reduced_name [epson_neon_test/.svn/wc.db-wal] > [/home/wwwdocs/svn/wolfgang] > [2013/03/12 12:47:19.261314, 3] smbd/vfs.c:1039(check_reduced_name) > check_reduced_name: epson_neon_test/.svn/wc.db-wal reduced to > /home/wwwdocs/svn/wolfgang/epson_neon_test/.svn/wc.db-wal > [2013/03/12 12:47:19.261349, 3] > smbd/trans2.c:5236(call_trans2qfilepathinfo) > call_trans2qfilepathinfo: SMB_VFS_STAT of epson_neon_test/.svn/wc.db-wal > failed (No such file or directory) > [2013/03/12 12:47:19.261385, 3] smbd/error.c:81(error_packet_set) > error packet at smbd/trans2.c(5238) cmd=50 (SMBtrans2) > NT_STATUS_OBJECT_NAME_NOT_FOUND > > > My question is, is this intended behaviour and just a downside of using a > network drive, or is this a bug? > > WCs on network drives have never been a recommended or officially supported configuration, due to variations in permissions handling & locking schemes between different protocols and implementations. As Subversion has moved more and more to a database-driven model for the WC, this has become more true from what I've gathered. > (Versions are Windows 7, Subversion client 1.7.8 > > What Samba version?
