----- Original Message ----- > From: "Vijay Bellur" <vbellur@xxxxxxxxxx> > To: "Dan Lambright" <dlambrig@xxxxxxxxxx>, "Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Saturday, February 7, 2015 7:45:49 PM > Subject: Re: readdir vs readdirp > > On 02/06/2015 02:03 PM, Dan Lambright wrote: > > Hi All, I hope this is not an overly stupid question.. > > > > Does anyone know a good way to test readdir (not readdirplus) on gluster? > > > > I see in : > > bugs/replicate/886998/strict-readdir.t > > > > .. that there is a switch "cluster.strict-readdir". It does not appear to > > work, or be referenced in the code - perhaps I am missing something. > > > > I also tried mounting nfs with the "nordirplus" option, this did not > > produce the desired results either, surprisingly. > > With fuse client, I suspect you would need to do the following to let > readdir fop percolate through the stack: > > 1. mount client with --use-readdirp=no. This will bypass readdirplus in > fuse. > > 2. Disable md-cache. md-cache by default converts all readdir operations > to readdirplus for its functioning. Thanks. This procedure worked, although rather than disabling md-cache, I used a switch to disable readdirp operations "*md-cache.force-readdirp=no". glusterfs --volfile-id=/t --volfile-server=gprfs018 /mnt2 --use-readdirp=no --xlator-option "*dht.use-readdirp=no" --xlator-option "*md-cache.force-readdirp=no" > > 3. Prevent dht from doing readdirp by default. While mounting, you could > pass --xlator-option "*dht.use-readdrip=no" to prevent readdir to > readdirp conversions in dht. > > -Vijay > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
