Bug 1005062 - SMB:dbench tests failed with datasync dir error :invalid argument on cifs mount.
Summary: SMB:dbench tests failed with datasync dir error :invalid argument on cifs mount.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: samba
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Raghavendra Talur
QA Contact: surabhi
URL:
Whiteboard: core
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-06 07:21 UTC by surabhi
Modified: 2015-12-03 17:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-03 17:14:06 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description surabhi 2013-09-06 07:21:29 UTC
Description of problem:
The dbench tests failed on cifs mount with datasync directory : invalid argument error.


Version-Release number of selected component (if applicable):
glusterfs-server-3.4.0.31rhs-1.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1.create a dis-rep volume
2.mount it via cifs on linux client
3.run dbench sanity script or run the following:

time /opt/qa/tools/dbench -t 300 -c /opt/qa/tools/dbench-4.0/client.txt -s -S 100

Actual results:
The dbench test failed with following errors:
[1147] datasync directory "./clients/client0/~dmtmp/WORD" failed: Invalid argument
  10      1156     0.35 MB/sec  execute  45 sec  latency 548.393 ms
  10      1160     0.35 MB/sec  execute  46 sec  latency 758.316 ms
[1147] datasync directory "./clients/client2/~dmtmp/WORD" failed: Invalid argument
[1147] datasync directory "./clients/client1/~dmtmp/WORD" failed: Invalid argument
[1176] datasync directory "./clients/client7/~dmtmp/WORD" failed: Invalid argument
  10      1165     0.34 MB/sec  execute  47 sec  latency 902.967 ms
  10      1167     0.33 MB/sec  execute  48 sec  latency 860.317 ms
[1176] datasync directory "./clients/client5/~dmtmp/WORD" failed: Invalid argument
[1176] datasync directory "./clients/client3/~dmtmp/WORD" failed: Invalid argument
  10      1172     0.33 MB/sec  execute  49 sec  latency 910.719 ms
[1176] datasync directory "./clients/client9/~dmtmp/WORD" failed: Invalid argument
[1176] datasync directory "./clients/client8/~dmtmp/WORD" failed: Invalid argument
  10      1176     0.32 MB/sec  execute  50 sec  latency 776.203 ms
  10      1180     0.32 MB/sec  execute  51 sec  latency 688.076 ms
[1176] datasync directory "./clients/client4/~dmtmp/WORD" failed: Invalid argument
[1176] datasync directory "./clients/client6/~dmtmp/WORD" failed: Invalid argument
[1176] datasync directory "./clients/client0/~dmtmp/WORD" failed: Invalid argument
[1200] datasync directory "./clients/client7/~dmtmp/WORD" failed: Invalid argument
[1176] datasync directory "./clients/client1/~dmtmp/WORD" failed: Invalid argument
  10      1186     0.31 MB/sec  execute  52 sec  latency 577.334 ms
[1176] datasync directory "./clients/client2/~dmtmp/WORD" failed: Invalid argument
[1200] datasync directory "./clients/client5/~dmtmp/WORD" failed: Invalid argument
[1211] datasync directory "./clients/client7/~dmtmp/WORD" failed: Invalid argument
[1200] datasync directory "./clients/client3/~dmtmp/WORD" failed: Invalid argument
  10      1196     0.31 MB/sec  execute  53 sec  latency 523.941 ms
[1200] datasync directory "./clients/client9/~dmtmp/WORD" failed: Invalid argument
[1211] datasync directory "./clients/client5/~dmtmp/WORD" failed: Invalid argument
[1211] datasync directory "./clients/client3/~dmtmp/WORD" failed: Invalid argument
[1200] datasync directory "./clients/client4/~dmtmp/WORD" failed: Invalid argument
[1200] datasync directory "./clients/client8/~dmtmp/WORD" failed: Invalid argument
[1200] datasync directory "./clients/client6/~dmtmp/WORD" failed: Invalid argument
  10      1207     0.30 MB/sec  execute  54 sec  latency 603.294 ms
[1200] datasync directory "./clients/client0/~dmtmp/WORD" failed: Invalid argument


Expected results:
Dbench sanity should pass.

Additional info:

Comment 2 Vivek Agarwal 2015-12-03 17:14:06 UTC
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.


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