Bug 1760168 - libgfapi:sometimes touch file failed by smb-4.8.3 cifs to access ec (4+2)*1 gluster-6 volume.
Summary: libgfapi:sometimes touch file failed by smb-4.8.3 cifs to access ec (4+2)*1 g...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi
Version: 6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-10 03:13 UTC by yinkui
Modified: 2020-03-12 13:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-12 13:24:23 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23547 0 None Abandoned libgfapi:sometimes touch file failed by smb-4.8.3 cifs to access ec (4+2)*1 gluster-6 volume. 2019-10-15 01:50:49 UTC

Description yinkui 2019-10-10 03:13:55 UTC
Description of problem:
Touching file failed when we access ec (4+2)*1 volume by samba-4.8.3 cifs.

Version-Release number of selected component (if applicable):
gluster-6.0
samba-4.8.3

How reproducible:


Steps to Reproduce:
1.server1: create ec (4+2)*1 volume test
2.server1: gluster v set test user.cifs on
3.client:  mount -t cifs -o username=root,password=foobar, \\\\server1\\test /root/dir
4.client: cd /root/dir && for i in `seq 1 10000`; do touch file-$i ; done

Actual results:
[root@client1 aa]# for i in `seq 1 10000`; do touch filee-$i ; done
touch: setting times of ‘filee-1501’: No such file or directory

Expected results:
Touch file-1 to file-10000 success.

Comment 1 Worker Ant 2019-10-14 11:07:55 UTC
REVIEW: https://review.gluster.org/23547 (libgfapi:sometimes touch file failed by smb-4.8.3 cifs to access ec (4+2)*1 gluster-6 volume.) posted (#1) for review on release-6 by None

Comment 2 Worker Ant 2020-03-12 13:24:23 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/1010, and will be tracked there from now on. Visit GitHub issues URL for further details


Note You need to log in before you can comment on or make changes to this bug.