Hide Forgot
Description of problem: When the same tier volume is mounted on the two different windows client. On one windows client i am able create text files but when i try to create a text file from other client, the files creation is denied permission. But when i tried to copy-paste a file from the share to the same share location it worked successfully. (eg. copy x:\file1 x:\) Version-Release number of selected component (if applicable): glusterfs-3.7.9-3.el7rhgs.x86_64 samba-client-libs-4.4.2-1.el7rhgs.x86_64 Windows Client 8.1 How reproducible: 8/10 Steps to Reproduce: 1.Mount tier volume (cold tier : Distributed-Disperse | 2 x (8 + 4) | Hot Tier Type : Distributed-Replicate 4 x 2 = 8) on two different windows client 2.Create text files in both 3.Copy file from the share to the same share Actual results: Creation of text file is denied in one of the windows client. Copy of the file successful. Expected results: Creation of files should be successful in both the windows client along with the copy of the file Additional info:
Additional info : Unmount and mount of the volume share in windows client has also been carried for the above issue.
what is the exact procedure to 'create a text file' ? Guessing: Right mouse button in explorer, chose new..., chose text file ?
and what is the name of the file that you attempted to create, so I can find the spot in the capture / log ?
OK... in the captures I see attempts to open "New Text Document.txt" with result ACCESS_DENIED. The capture seems to be confusing wireshark sometimes, too, since sometimes it interprets a READ RESPONSE as the reply to the create request (e.g. request in frame 14704 with response in frame 15790 ...). The logs are again rather useless since it only collects log.smbd from /var/log/samba, which is not the main samba log file, and it is rotated at 50K, which is not enough. /var/log/messages contains some lvl-0 messages though: May 2 14:13:16 localhost smbd[12517]: remove_oplock: update_num_read_oplocks failed for file New Microsoft Word Document.docx, fnum 3607849963, 616a7a47:8eae8005c4ccc23b:0 May 2 14:13:21 localhost smbd[1735]: glfs_stat(New Microsoft Word Document.docx) failed: Invalid argument ... May 2 14:54:07 localhost smbd[1735]: glfs_stat(New Text Document.txt) failed: Stale file handle ... May 2 14:54:43 localhost smbd[1735]: remove_oplock: update_num_read_oplocks failed for file New Microsoft Word Document.docx, fnum 964554519, ce7f023f:948edf52dced7f6a:0 ... May 2 14:57:38 localhost smbd[1735]: glfs_stat(New Text Document.txt) failed: Invalid argument lots of those. Maybe the libgfapi experts can comment on those?
best I know, we currently support neither EC nor tiering with Samba. If we decide to support it and if this reoccurs, we need a new bug.