Re: [Nfs-ganesha-devel] Any plans to support callback API model for FSALs?

2017-09-14 Thread Kinglong Mee
Hello Daniel, I am interested in the ASYNC API for FSALs. Could you show me some information (plan, document, discussion) about it? If there is a draft of source about it, I am happy to help with the testing. thanks, Kinglong Mee On Thu, May 11, 2017 at 10:40 PM, Daniel Gryniewicz wrote

[Nfs-ganesha-devel] The life of tcp drc

2017-10-12 Thread Kinglong Mee
e_t. Otherwise, don't put the reference at #2, when to put it? the bad case is the drc ref always be 1 forever, am I right? thanks, Kinglong Mee -- Check out the vibrant tech community on one of the world's

[Nfs-ganesha-devel] The life of tcp drc

2017-10-12 Thread Kinglong Mee
. Otherwise, don't put the reference at #2, when to put it? the bad case is the drc ref always be 1 forever, am I right? thanks, Kinglong Mee -- Check out the vibrant tech community on one of the world's

Re: [Nfs-ganesha-devel] The life of tcp drc

2017-10-13 Thread Kinglong Mee
Hi Malahal, Thanks for your reply. #1. I'd like to post a patch to delete it, because I have some cleanups for drc. #2/#3. Sorry for my missing of nfs_rpc_free_user_data(). With it, everything is okay. thanks, Kinglong Mee On 10/13/2017 15:52, Malahal Naineni wrote: > #1. Looks li

[Nfs-ganesha-devel] ganesha crash when stopping with gluster handles exist

2018-01-24 Thread Kinglong Mee
With the latest codes (nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64), set ganesha.conf includes, CACHEINODE { Dir_Max = 50; Dir_Chunk = 0; } that forces mdcache_readdir enter mdcache_dirent_populate, but mdc_add_cache return ERR_FSAL_OVERFLOW when a directory contains larger than 50 files (

[Nfs-ganesha-devel] Ganesha caches bad directory entries when other glusterfs client(ganesha) creating files

2018-02-10 Thread Kinglong Mee
t entries from the same name directory; 6. GaneshaB gets the brick2's mtime as the directory's mtime; 7. At bad case, ganeshaB caches those entries (without the file created at #4). Is it a known issue? Maybe we should update the directory&#x

[Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

2018-03-06 Thread Kinglong Mee
When using nfsv3 on glusterfs-3.13.1-1.el7.x86_64 and nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64, I gets strange "Invalid argument" when writing file. 1. With quota disabled; nfs client mount nfs-ganesha share, and do 'll' in the testing directory. 2. Enable quota; # getfattr -d -m . -e hex /roo

Re: [Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

2018-03-06 Thread Kinglong Mee
On 2018/3/7 10:59, Kinglong Mee wrote: > When using nfsv3 on glusterfs-3.13.1-1.el7.x86_64 and > nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64, > I gets strange "Invalid argument" when writing file. > > 1. With quota disabled; > nfs client mount nfs-ganesha share

Re: [Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

2018-03-07 Thread Kinglong Mee
On 2018/3/7 21:10, Daniel Gryniewicz wrote: > On 03/06/2018 10:10 PM, Kinglong Mee wrote: >> On 2018/3/7 10:59, Kinglong Mee wrote: >>> When using nfsv3 on glusterfs-3.13.1-1.el7.x86_64 and >>> nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64, >>> I gets strange

Re: [Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

2018-03-11 Thread Kinglong Mee
On Thu, Mar 8, 2018 at 10:17 PM Daniel Gryniewicz wrote: > On 03/07/2018 10:21 PM, Kinglong Mee wrote: > > On 2018/3/7 21:10, Daniel Gryniewicz wrote: > >> On 03/06/2018 10:10 PM, Kinglong Mee wrote: > >>> On 2018/3/7 10:59, Kinglong Mee wrote: > >>>&g

[Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

2017-04-12 Thread Kinglong Mee
When I testing ganesha nfs bases on glusterfs, the runltp always warning as, rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea14f5’: Device or resource busy rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/rmderQsjV’: Directory not empty and, "rmderQsjV" also contains files at the b

Re: [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

2017-04-12 Thread Kinglong Mee
e. > > On Apr 12, 2017 8:06 PM, "Kinglong Mee" <mailto:mijinl...@open-fs.com>> wrote: > > When I testing ganesha nfs bases on glusterfs, the runltp always warning > as, > > rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea14f5’: &

Re: [Nfs-ganesha-devel] Device or resource busy when runltp cleanup test-files

2017-04-12 Thread Kinglong Mee
ent-0 gvtest-client-1 end-volume volume gvtest type debug/io-stats option count-fop-hits off option latency-measurement off option log-level INFO subvolumes gvtest-dht end-volume thanks, Kinglong Mee On 4/13/2017 10:17, Malahal Naineni wrote: > Sorry, I missed your not

Re: [Nfs-ganesha-devel] [Gluster-devel] Device or resource busy when runltp cleanup test-files

2017-04-20 Thread Kinglong Mee
Sorry for the late reply. On 4/16/2017 22:31, Vijay Bellur wrote: > > > On Wed, Apr 12, 2017 at 10:37 PM, Kinglong Mee <mailto:mijinl...@open-fs.com>> wrote: > > Yes, this one is silly rename, > > >>> rm: cannot remove > ‘/mnt/nfs/ltp-JEYAuk

[Nfs-ganesha-devel] About the time accuracy of dirent in mdcache

2017-07-17 Thread Kinglong Mee
mtime.tv_usec? Are there some problems or some other considers? thanks, Kinglong Mee -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/sla

Re: [Nfs-ganesha-devel] About the time accuracy of dirent in mdcache

2017-07-18 Thread Kinglong Mee
On 7/18/2017 20:54, Daniel Gryniewicz wrote: > On 07/18/2017 08:51 AM, Daniel Gryniewicz wrote: >> On 07/17/2017 08:10 PM, Kinglong Mee wrote: >>> Ganesha invalidates directory dirent in mdcache_getattrs depends on >>> mtime.tv_sec. >>> But the time accur