Hi,
yes, in test code there was such issue. The production code that occasionally
has issues with first time accessing the file however has proper parameters in
use when opening a file.
In production the issue is now gone when the same file being read/written is no
longer locked with another
Hi, Gluster Expert,
Sorry for wrong code "open(argv[1], O_CREAT|O_RDWR|S_IRUSR|S_IWUSR) "in
previous mail, after correct it , the issues seems GONE.
But I still confuse why wrong code not failed in EXT4 file system.
After I check tcpdump packet via network, it show that in CREATE process, the
Hi, Gluster expert,
I has just raise a bug with https://bugzilla.redhat.com/show_bug.cgi?id=1529237
on gluster community.
I also attached the reproduce source code and shell script here FYI.
>From my investigation , I suppose the issue maybe caused by "cache in client
>is invalid but the file
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-12-28-3f0405f3
___
Gluster-devel mailing list
Gluster-devel@gluster.org
Hi All,
To reduce the overall time taken by every regression job for all the
glusterd tests, we are thinking of optimizing glusterd tests so that some
of the duplicate tests can be avoided if we can group them based on types
of volumes, operations to be performed, test to be performed on single
Hi,
https://review.gluster.org/#/c/19070/2 modifies posix_lookup() to remove
stale .glusterfs entry during gfid (nameless) lookup.
The initial version (v1) of the patch attempted to remove it in
posix_symlink in order to fix BZ 1529488 but the in the review
discussions (see the patch), it was
