Re: [Gluster-devel] [Gluster-Maintainers] Maintainers 2.0 Proposal

In light of community conversations, I've put some revisions on the Maintainers changes, outlined in the hackmd pad: https://hackmd.io/s/SkwiZd4qe Feedback welcomed! Note that the goals of this are to expand out our reach as a project (Gluster.org) and make it easy to define who's a maintainer

Re: [Gluster-devel] [Gluster-users] [gluster-devel][gluster-users] Usability Initiative for Gluster: Documentation

Thanks for the initiative Amye! On Thu, Apr 13, 2017 at 11:36 PM, Amye Scavarda wrote: > One of the things that we're taking on for Gluster as a project is > improving our usability overall - user experience, developer experience, > contributor experience. We want Gluster to be

[Gluster-devel] Coverity covscan for 2017-04-13-af218797 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-04-13-af218797 ___ Gluster-devel mailing list Gluster-devel@gluster.org

[Gluster-devel] [gluster-devel][gluster-users] Usability Initiative for Gluster: Documentation

One of the things that we're taking on for Gluster as a project is improving our usability overall - user experience, developer experience, contributor experience. We want Gluster to be fun to work with. As part of this, we'll be working on improving our overall documentation. Improving

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

Sorry, I missed your note below. This is definitely due to an NFS client's silly rename. All ".nfs" are due to silly rename implementation in NFS client. You might want to read about it. >> rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea14f5’: >> Device or resource busy On

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

Yes, this one is silly rename, >>> rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/.nfsaa46457a6a72f8ea14f5’: >>> Device or resource busy But, the other one isn't client's silly rename, rm: cannot remove ‘/mnt/nfs/ltp-JEYAuky2dz/rmderQsjV’: Directory not empty Also, the second

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

What are the file names under the directory? What does "ls -la" show both at the client and at the server in that directory? On Thu, Apr 13, 2017 at 5:13 AM, Kinglong Mee wrote: > There are some files under "rmderQsjV" (that's not a silly rename dir) really > at underlying

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

There are some files under "rmderQsjV" (that's not a silly rename dir) really at underlying filesystem, but the nfs client shows empty. Are there some problems in MDCACHE or cache timeouts? On 4/12/2017 22:48, Malahal Naineni wrote: > Could be due to NFS client silly rename. > > On Apr 12,

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

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

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

Could be due to NFS client silly rename. On Apr 12, 2017 8:06 PM, "Kinglong Mee" wrote: > 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

Re: [Gluster-devel] [Gluster-users] Glusterfs meta data space consumption issue

Il 12/04/2017 14:16, ABHISHEK PALIWAL ha scritto: > I have did more investigation and find out that brick dir size is > equivalent to gluster mount point but .glusterfs having too much > difference > You are probably using sharding? Buon lavoro. /Alessandro Briosi/ *METAL.it Nord S.r.l.* Via

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

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

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On 04/13/2017 11:32 AM, Atin Mukherjee wrote: On Thu, Apr 13, 2017 at 8:17 PM, Shyam > wrote: On 02/28/2017 10:17 AM, Shyam wrote: Hi, With release 3.10 shipped [1], it is time to set the dates for release

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On Thu, Apr 13, 2017 at 8:17 PM, Shyam wrote: > On 02/28/2017 10:17 AM, Shyam wrote: > >> Hi, >> >> With release 3.10 shipped [1], it is time to set the dates for release >> 3.11 (and subsequently 4.0). >> >> This mail has the following sections, so please read or revisit as

Re: [Gluster-devel] Announcing release 3.11 : Scope, schedule and feature tracking

On 02/28/2017 10:17 AM, Shyam wrote: Hi, With release 3.10 shipped [1], it is time to set the dates for release 3.11 (and subsequently 4.0). This mail has the following sections, so please read or revisit as needed, - Release 3.11 dates (the schedule) - 3.11 focus areas Pinging the list

[Gluster-devel] Community Meeting minutes for 12 April 2017

No meeting was held on 2017-03-29. Zero people responded to the roll call. (Possibly due to many being at the Vault storage conference.) Also a very low turnout for this meeting — only five people and myself. The next meeting is on 26 April 2017 at 15:00 UTC (11AM EDT, 8AM PDT) or `date -d

Re: [Gluster-devel] [Gluster-users] Glusterfs meta data space consumption issue

On Thu, Apr 13, 2017 at 12:19 PM, ABHISHEK PALIWAL wrote: > yes it is ext4. but what is the impact of this. > Did you have a lot of data before and you deleted all that data? ext4 if I remember correctly doesn't decrease size of directory once it expands it. So in ext4

Re: [Gluster-devel] [Gluster-users] Glusterfs meta data space consumption issue

yes it is ext4. but what is the impact of this. On Thu, Apr 13, 2017 at 9:26 AM, Pranith Kumar Karampuri < pkara...@redhat.com> wrote: > Yes > > On Thu, Apr 13, 2017 at 8:21 AM, ABHISHEK PALIWAL > wrote: > >> Means the fs where this brick has been created? >> On Apr