Description of problem: We used git version from 12th June (ie. yesterday) on Fedora 18 with 3.9.5 kernel. local filesystem on client = xfs underlaying filesystem on both servers (replica 2x of 1 brick) xfs on lvm input file on local system generated: 4633 B of random numbers repeated to file size 4688596000 , name = rndcore . File rndcore on local disc copied from client to glusterfs volume, mounted via nfs : cp -av rndcore /gluster_m/gs-home-u/ycore ‘rndcore’ -> ‘/gluster_m/gs-home-u/ycore’ cp: writing ‘/gluster_m/gs-home-u/ycore’: Unknown error 527 cp: failed to extend ‘/gluster_m/gs-home-u/ycore’: Unknown error 527 when mounted natively via fuse, write fails with bad file handle error Glusterfs vol. size = 2TB. This bug is observed also with native gluster client. Version-Release number of selected component (if applicable): How reproducible: always. Just use cp to copy big files. Steps to Reproduce: 1. cp /local/fs/bigfile /mounted/gluster/ Actual results: cp -av rndcore /gluster_m/gs-home-u/ycore ‘rndcore’ -> ‘/gluster_m/gs-home-u/ycore’ cp: writing ‘/gluster_m/gs-home-u/ycore’: Unknown error 527 cp: failed to extend ‘/gluster_m/gs-home-u/ycore’: Unknown error 527 or bad file handle error Expected results: copy file correctly Additional info:
gluster volume transport was rdma only. While testing with primitive custom copy C programm, syscall write() did not work reliably with bigger butter e.g. 120kB, 1MB ... (sometimes work, sometimes fail) . Copying of 4.2GB file with buffer size 4096B was slow, but mostly worked.
pre-release version is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.