[Nfs-ganesha-devel] V2.5-stable + vmware
This list has been deprecated. Please subscribe to the new devel list at lists.nfs-ganesha.org.Hello, I am testing if v2.5 for FSAL Ceph work with vmware client. For version 3.0, it works. But for version 4.1, there is no tcp packets exchanged from server to client and connection always timeout. Is it a known issue somehow? Is 4.1 supported for v2.5 and FSAL ceph. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] NFS-Ganesha Project board now public
Hello all, Now Github supports public organization board.[1] NFS-Ganesha project board is publicly visible. Only project members can edit cards, but everyone can see the board. We can actively use the board to track bugs, features and owners for each version. [1] https://blog.github.com/2018-03-28-improved-organization-project-permissions/#public-organization-projects [2] https://github.com/orgs/nfs-ganesha/projects Thanks, Surpiti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] New things in feature board
Hi Sriram, Earlier we had boards at the repo level (https://github.com/nfs-ganesha/nfs-ganesha/projects), but there were some permission issues, and it could be viewed by everyone but not all can add cards. So we moved the board to organization level. But sadly, according to this (https://github.com/isaacs/github/issues/935) only those who are members of organization can view the board. Possible solution would be to figure out if we can move this board again to repo level, and figure out permissions. Meanwhile, Frank has rights to add people in organization. Github permissions are bit inconvenient. -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) >>> Sriram Patil <srir...@vmware.com> 02/08/18 12:30 PM >>> Hi Supriti, The link you have provided is not working. And the 2.7 board seems to be closed. I checked things here - https://github.com/nfs-ganesha/nfs-ganesha/projects. Am I missing something? Thanks, Sriram From: Supriti Singh <supriti.si...@suse.com> Date: Thursday, February 8, 2018 at 2:14 PM To: "nfs-ganesha-devel@lists.sourceforge.net" <nfs-ganesha-devel@lists.sourceforge.net> Subject: [Nfs-ganesha-devel] New things in feature board Hello all, I am trying new things in our project board. Let me know if the approach is okay, or you would like to change something. 1. Adding issues in github: It seems like only when there is an issue, I can assign it to the developer actively working on it. For example, in 2.7 board I have created a issue for "FSAL_PSEDUO" reference and assigned to Frank for now (as an example). https://github.com/orgs/nfs-ganesha/projects/1 If you are not planning to work actively on it for this release cycle, feel free to move it in backlog or reassign to someone else. 2. New label "should_be_backported" I have created a new label for our github issue to mark the bug fix that we would like to backport for earlier version as well. 3. New board: NFS-Ganesha wish list Treat this as a dumping ground for all things that you want but don't have time. With increasing community, we new members would be excited to work on them. I have added link to Frank's google doc on Ganesha punch list. 4. NFS-Ganesha 2.6 board: As NFS-Ganesha 2.6 is feature complete, I am using this board to track if we have test coverage and documentation for key features. If not, we can focus on adding them. 5. Automation in board: I will set rules in board, so that whenever an issue is closed, it moves automatically to done. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] New things in feature board
Hello all, I am trying new things in our project board. Let me know if the approach is okay, or you would like to change something. 1. Adding issues in github: It seems like only when there is an issue, I can assign it to the developer actively working on it. For example, in 2.7 board I have created a issue for "FSAL_PSEDUO" reference and assigned to Frank for now (as an example). https://github.com/orgs/nfs-ganesha/projects/1 If you are not planning to work actively on it for this release cycle, feel free to move it in backlog or reassign to someone else. 2. New label "should_be_backported" I have created a new label for our github issue to mark the bug fix that we would like to backport for earlier version as well. 3. New board: NFS-Ganesha wish list Treat this as a dumping ground for all things that you want but don't have time. With increasing community, we new members would be excited to work on them. I have added link to Frank's google doc on Ganesha punch list. 4. NFS-Ganesha 2.6 board: As NFS-Ganesha 2.6 is feature complete, I am using this board to track if we have test coverage and documentation for key features. If not, we can focus on adding them. 5. Automation in board: I will set rules in board, so that whenever an issue is closed, it moves automatically to done. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Features board list
Good, then we can go ahead with this board: https://github.com/orgs/nfs-ganesha/projects/1 I have added few columns to get started. We can modify it to suit our needs better. Main developers can add cards that they are working on, and plan to work on. I would be happy to manage the board (adding label, linked issues etc.) Thanks again. -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) >>> William Allen Simpson <william.allen.simp...@gmail.com> 02/01/18 4:21 PM >>> On 2/1/18 8:04 AM, Supriti Singh wrote: > It seems like github does not support organization level board to be visible. > https://github.com/isaacs/github/issues/935 :/ > Let's just keep this design. If github already knows about the issue, then maybe they'll fix it. My problem is that I only rarely log in, perhaps once a week, whenever I'm making a ntirpc pullup request. Unlike gerrithub, github handles email replies. So github is better for workflow. > I forgot to ask first, but is there already a trello board for nfs-ganesha? I > can see mention of nfs-ganesha in > gluster[1] and ceph[2][3] trello board. If yes and if that can be made > public, then we would not need github project > boards. > > [1] https://trello.com/c/AhGWdQYh/104-protocol-support-nfs-ganesha-samba > [2] https://trello.com/c/6DHdMUyH/144-cephfs-manila-nfs-ganesha > [3] https://trello.com/c/6DHdMUyH/144-cephfs-manila-nfs-ganesha > > Nicer to have on the github project. Those are FSAL specific, and not well coordinated. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Features board list
It seems like github does not support organization level board to be visible. https://github.com/isaacs/github/issues/935 :/ Maybe Frank can fix the permission issue for the other boards. I forgot to ask first, but is there already a trello board for nfs-ganesha? I can see mention of nfs-ganesha in gluster[1] and ceph[2][3] trello board. If yes and if that can be made public, then we would not need github project boards. [1] https://trello.com/c/AhGWdQYh/104-protocol-support-nfs-ganesha-samba [2] https://trello.com/c/6DHdMUyH/144-cephfs-manila-nfs-ganesha [3] https://trello.com/c/6DHdMUyH/144-cephfs-manila-nfs-ganesha -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) >>> William Allen Simpson <william.allen.simp...@gmail.com> 01/31/18 11:31 PM >>> >>> On 1/31/18 1:11 PM, Supriti Singh wrote: > I have created a new board here: https://github.com/orgs/nfs-ganesha/projects > . Its organization-wide project board. Everyone who belongs to nfs-ganesha organization should have write access. Can you check if you have write access to this board. YES! But the page isn't visible (404 error) until I've logged in. The other board was visible even not logged in. That would be handy. > It makes > more sense to have organization wide board, as we can track ntirpc and > ci-tests development features as well. > Good idea. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] Features board list
Hello all, As discussed in community call, I am sharing the feature board list: https://github.com/nfs-ganesha/nfs-ganesha/projects for nfs-ganesha 2.6 and 2.7. The aim is to use these boards to track the planned features for major release. The hope is that it will help community members to follow up on feature development, and do more focused testing. In the project board, ideally everyone who has write access to nfs-ganesha github should be able to modify the board. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] NFS-Ganesha and compatible ceph version
Hi Daniel, Thanks for reply. Does it mean that 2.7 will already be ready to support containerized nfs-ganesha? Are there more details on what exact features need to be implemented in nfs-ganesha and cephfs to make OpenShift/Kubernerties work. I am aware of blog post by Jeff: https://jtlayton.wordpress.com/2017/11/07/active-active-nfs-over-cephfs/. It would be really helpful if we can get more details. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) >>> Daniel Gryniewicz <d...@redhat.com> 01/09/18 3:45 PM >>> Yes, 2.7 will be compatible with mimic, and likely with luminous as well, since features for Ganesha tend to be backported in Ceph. The only major work I'm aware of coming for Ceph/Ganesha is HA on OpenShift/Kuberneties for FSAL_CEPH, and full in-place read/write for FSAL_RGW. I'm sure lots of little things will be added, as usual. Daniel On Tue, Jan 9, 2018 at 4:52 AM, Supriti Singh <supriti.si...@suse.com> wrote: > Hello, > > As v2.6-rc1 was recently tagged, I assume the work will start very soon for > 2.7. If yes, then is 2.7 targeted to be compatible with ceph mimic? Also, > what are the main features list aimed for 2.7? > > Thanks, > Supriti > > -- > Supriti Singh > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] NFS-Ganesha and compatible ceph version
Hello, As v2.6-rc1 was recently tagged, I assume the work will start very soon for 2.7. If yes, then is 2.7 targeted to be compatible with ceph mimic? Also, what are the main features list aimed for 2.7? Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Weekly meeting link
I have updated the meeting id in wiki: https://github.com/nfs-ganesha/nfs-ganesha/wiki/Developers Not sure about the Browser and Lync meeting ids though. -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) >>> sriram patil <spsrirampa...@gmail.com> 01/08/18 8:10 PM >>> Thank you, Frank. - Sriram On 08-Jan-2018 11:15 PM, "Frank Filz" <ffilz...@mindspring.com> wrote: Meetings currently are at 7:30 AM PST, which is 9:00 PM IST. The meeting URL is: https://bluejeans.com/373354489 Frank From: sriram patil [mailto:spsrirampa...@gmail.com] Sent: Monday, January 8, 2018 9:05 AM To: nfs-ganesha-devel@lists.sourceforge.net Subject: [Nfs-ganesha-devel] Weekly meeting link Hi, Can anyone share the weekly meeting link? I tried the link from github wiki few weeks back and it did not work for some reason. Also, as far as I know the weekly meeting timings are 10PM IST every Tuesday. Please let me know if there is any change in that as well. Thanks, Sriram This email has been checked for viruses by Avast antivirus software. www.avast.com -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] ganesha dashboard on github
Hi Frank,
In the board, for each column ("Planned", "In Progress" and "Done"), there is a
'+' sign in the right most corner. You
can use that to add new cards. I added a test card.
Regarding permissions, my guess is that it should work for anyone who has
permission to that github repo. Let me know if
you are still unable to add cards.
Thanks,
Supriti
--
Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham
Norton,
HRB 21284 (AG Nürnberg)
>>> "Frank Filz" <ffilz...@mindspring.com> 10/04/17 12:32 AM >>>
> On 09/21/17 15:32, Frank Filz wrote:
> > Sent you an invite to join the github project, once you accept let me know
> if you still can't edit.
> >
> > Frank
>
> I still don't success in adding anything to the board. It's maybe only
> because I
> don't know how doing after loading the borad page :
>
> https://github.com/nfs-ganesha/nfs-ganesha/projects/1 .
Supriti, do you have any thoughts here? Do people need more github permission
or something?
Frank
> >> -Original Message-
> >> From: LUCAS Patrice [mailto:patrice.lu...@cea.fr]
> >> Sent: Thursday, September 21, 2017 2:11 AM
> >> To: Frank Filz <ffilz...@mindspring.com>
> >> Subject: ganesha dashboard on github
> >>
> >> Hello Frank,
> >>
> >>
> >> It's look like I can't edit the newly ganesha 2.6 dashboard on github.
> >> Do I need smth special to be able to do that ? (my github login is
> >> patlucas)
> >>
> >>
> >> Best regards,
> >>
> >> --
> >> Patrice LUCAS
> >> Ingenieur-Chercheur, CEA-DAM/DSSI/SISR/LA2S tel : +33 (0)1 69 26 47
> >> 86 e- mail : patrice.lu...@cea.fr
> >
> > ---
> > This email has been checked for viruses by Avast antivirus software.
> > https://www.avast.com/antivirus
> >
>
> --
> Patrice LUCAS
> Ingenieur-Chercheur, CEA-DAM/DSSI/SISR/LA2S tel : +33 (0)1 69 26 47 86 e-
> mail : patrice.lu...@cea.fr
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] New board on github to track features
Hello all, Currently we don't have a central place for community where we plan or track the planned features or bugs for upcoming release 2.6. I am only aware of this doc: https://docs.google.com/document/d/1wJCMM6g9Ahc9TNDgBByQlyCDRWegtv-lI0cPYu_tTns/edit. Yesterday on IRC, Frank and I discussed regarding utilizing the github project page (https://github.com/nfs-ganesha/nfs-ganesha/projects) to track the features for next release 2.6. The page would be similar to kanban-style board, where we can assign task, track progress. We can even have individual boards for each FSAL and individual component (if required) as well. I would be happy to create boards, but currently I don't have permissions. It would be really helpful to have some tracking mechanism for community. If someone has any other suggestions,please suggest. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Known limitations of FSAL Ceph
Thank you for opening ticket on ceph tracker. For now, is someone already aware of known limitations for FSAL Ceph. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) >>> Ramana Raja <rr...@redhat.com> 08/29/17 5:41 PM >>> Thanks for raising this. I've created a Ceph tracker ticket for now, http://tracker.ceph.com/issues/21172 Documentation on NFS-Ganesha/CephFS integration is missing. -Ramana On Tue, Aug 29, 2017 at 6:04 PM, Daniel Gryniewicz <d...@redhat.com> wrote: > > Not that I'm aware of. Matt (on the RGW team) wrote that, and as far as > I know, no one from the CephFS team has written a similar document. > > Daniel > > On 08/29/2017 02:27 AM, Supriti Singh wrote: > > Hello, > > > > For FSAL RGW, > > https://github.com/ceph/ceph/blob/master/doc/radosgw/nfs.rst#supported-operations > > this list down the operations that are not supported with FSAL RGW > > currently. > > > > Is there a similar list for FSAL Ceph as well? > > > > Thanks, > > Supriti > > > > -- > > Supriti Singh > > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > > HRB 21284 (AG Nürnberg) > > > > > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > > > > > ___ > > Nfs-ganesha-devel mailing list > > Nfs-ganesha-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] Known limitations of FSAL Ceph
Hello, For FSAL RGW, https://github.com/ceph/ceph/blob/master/doc/radosgw/nfs.rst#supported-operations this list down the operations that are not supported with FSAL RGW currently. Is there a similar list for FSAL Ceph as well? Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Weekly conference call timing
Hi Frank, For me Thursday 4.30 pm to 5.30 pm paris time works. And Friday anytime is good. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) >>> "Frank Filz" <ffilz...@mindspring.com> 08/09/17 9:49 PM >>> My daughter will be starting a new preschool, possibly as early as August 22nd. Unfortunately since it's Monday, Tuesday, Wednesday and I will need to drop her off at 9:00 AM Pacific Time, which is right in the middle of our current time slot... We could keep the time slot and move to Thursday (or even Friday), or I could make it work to do it an hour earlier. I'd like to make this work for the largest number of people, so if you could give me an idea of what times DON'T work for you that would be helpful. 7:30 AM to 8:30 AM Pacific Time would be: 10:30 AM to 11:30 AM Eastern Time 4:30 PM to 5:30 PM Paris Time 8:00 PM to 9:00 PM Bangalore Time (and 9:00 PM to 10:00 PM when we switch back to standard time) If there are other time zones we have folks joining from, please let me know. Thanks Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] DBUS patch
Hi Saumya, Besides "shutdown", I have also tried "grace" signal. It also can be also triggered by non root. My guess would be that other methods in the interface "org.ganesha.nfsd.admin" would behave the same. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) >>> Soumya Koduri <skod...@redhat.com> 07/24/17 11:45 AM >>> Hi Supriti, On 07/24/2017 01:07 PM, Supriti Singh wrote: > Hello all, > > I have submitted a new patch https://review.gerrithub.io/#/c/370835/ to allow > only root users to access the dbus.In the > current dbus configuration, there are some security issues. For example, even > a non-root user can call shutdown on a > ganesha process started by root. The easiest way to fix is to allow only root > for now. Apart from shutting down ganesha process, are there any other security issues which you are aware of? We had one user reporting a security threat with using DBus a while ago but hadn't provided much details. > > For 2.6, we can have a better solution. As I understood, the plan is to > support non-root as well in future. May be we > can have either a user group "ganesha" and we allow only these users to have > access. +1 This is simple and similar to what Kaleb had suggested to make ganesha process be able to run by non-root user. But yes instead of tweaking the .conf file manually, if no one objects we can add it to default configuration. > > The other solution would be to handle authorization in code. For example, > using api dbus_bus_get_unix_user() > [https://dbus.freedesktop.org/doc/api/html/group__DBusBus.html#ga24d782c710f3d82caf1b1ed582dcf474] > I have just started > looking into it. May be this solution is intrusive and hard to maintain. I > will research a bit more. > > Please let me know your thoughts. I do not know how complicated it shall be, but as long as there is a way for ganesha service to get credentials of the user executing dbus command to compare with this unix_user, it should be good IMO. Thanks, Soumya [1] http://seclists.org/oss-sec/2016/q4/349 > > Thanks, > Supriti > > -- > Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham > Norton, > HRB 21284 (AG Nürnberg) > > > > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] DBUS patch
Hello all, I have submitted a new patch https://review.gerrithub.io/#/c/370835/ to allow only root users to access the dbus.In the current dbus configuration, there are some security issues. For example, even a non-root user can call shutdown on a ganesha process started by root. The easiest way to fix is to allow only root for now. For 2.6, we can have a better solution. As I understood, the plan is to support non-root as well in future. May be we can have either a user group "ganesha" and we allow only these users to have access. The other solution would be to handle authorization in code. For example, using api dbus_bus_get_unix_user() [https://dbus.freedesktop.org/doc/api/html/group__DBusBus.html#ga24d782c710f3d82caf1b1ed582dcf474] I have just started looking into it. May be this solution is intrusive and hard to maintain. I will research a bit more. Please let me know your thoughts. Thanks, Supriti -- Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] NFS-Ganesha HA
So at the moment the direction is more to use pacemaker/corosync and each FSAL its own way to handle the client state in shared storage. Looking at storhaug, it seems like the plan is to use the same resource agent for both gluster and ceph (cephfs and rgw) backend. We need to point to different shared storage in the resource agent as per the backend FSAL. For Ceph in particular, can you please point out the development effort. I am aware of patch submitted by Gui using rados kv as backend(https://review.gerrithub.io/#/c/355070/). Are there changes required in ceph side of code also? Thanks, Supriti -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) >>> "Frank Filz" <ffilz...@mindspring.com> 07/05/17 3:36 PM >>> > CMAL is dead. There wasn't enough interest in it, and the majority of it's > features are provided by whatever clustered filesystem is backing Ganesha. CMAL is dead, long live CMAL! What came out of the CMAL effort was a couple things: 1. The dBus interface we have for clustering (takeip, releaseip, entergrace) is needed by everyone, no need to make that part pluggable 2. Everyone at the time was using shared storage for client recovery information 3. Clusterized DRC seemed like too big a thing On the other hand, the pluggable backend for the client recovery information is really just part of the CMAL ideas under a new name... > There are plans underway to extend the FSAL APIs to support more features > required by HA. It's unlikely that we'll ever be able to run active/active > without a framework like pacemaker/corosync, but it's not impossible. > > Note that storhaug for Gluster does do active/active, so it's certainly > possible. Work for Ceph is still in progress. > > Daniel Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] nfs ganesha centos ci tests - posix compliance
Hi Arthy, Can you also provide link to the exact test, if possible? Thanks, Supriti -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) >>> Arthy Loganathan <aloga...@redhat.com> 06/22/17 8:04 AM >>> Hi All, I have added new test in upstream nfs-ganesha centos ci which runs posix compliance test suite on v3 and v4 mount. Centos ci job link - https://ci.centos.org/view/NFS-Ganesha/job/nfs_ganesha_posix_compliance/ The job gets triggered automatically for every patchset created and reports back the result. Please try using the job and share your comments. Thanks & Regards, Arthy -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Mount connection timeout
Thanks for hints. I will try and see if I can figure out what could be the problem. -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) >>> Daniel Gryniewicz <d...@redhat.com> 06/20/17 4:40 PM >>> You may also want to get a packet trace of the exchange. Daniel On 06/20/2017 09:45 AM, Frank Filz wrote: > What debug logging do you have enabled? > > > > You may want to look at NFS4 component and maybe DISPATCH. > > > > Frank > > > > *From:*Supriti Singh [mailto:supriti.si...@suse.com] > *Sent:* Tuesday, June 20, 2017 1:38 AM > *To:* ffilz...@mindspring.com; mbenja...@redhat.com > *Cc:* nfs-ganesha-devel@lists.sourceforge.net > *Subject:* Re: [Nfs-ganesha-devel] Mount connection timeout > > > > Is there a way to debug it further? It happens most of the time when I > restart the nfs-ganesha service. The first mount command returns > timeout. When I reissue the command, it works. > > > > -- > > Supriti Singh > > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > > HRB 21284 (AG Nürnberg) > > >>>> Matt Benjamin <mbenja...@redhat.com <mailto:mbenja...@redhat.com>> >>>> 06/19/17 9:42 PM >>> > yeah > > - Original Message - >> From: "Frank Filz" <ffilz...@mindspring.com <mailto:ffilz...@mindspring.com>> >> To: "Supriti Singh" <supriti.si...@suse.com <mailto:supriti.si...@suse.com>>, > nfs-ganesha-devel@lists.sourceforge.net > <mailto:nfs-ganesha-devel@lists.sourceforge.net> >> Sent: Monday, June 19, 2017 9:46:32 AM >> Subject: Re: [Nfs-ganesha-devel] Mount connection timeout >> >> >> >> That’s just LRU running and not finding any work to do. I’m not sure those >> messages should be LogDebug, maybe they should be LogFullDebug. >> >> >> >> Frank >> >> >> >> >> From: Supriti Singh [mailto:supriti.si...@suse.com] >> Sent: Monday, June 19, 2017 4:47 AM >> To: nfs-ganesha-devel@lists.sourceforge.net > <mailto:nfs-ganesha-devel@lists.sourceforge.net> >> Subject: [Nfs-ganesha-devel] Mount connection timeout >> >> >> >> >> I am using nfs-ganesha v2.5-final + CephFS FSAL. I have noticed that when I >> mount, sometimes first mount attempt fails with connection time out. And it >> succeed in later attempts. >> >> In event of timeout, the log contains the following lines many times: >> >> ganesha.nfsd-4274[cache_lru] lru_run :INODE LRU :DEBUG :After work, >> open_fd_count:0 count:5 fdrate:1 threadwait=90 >> ganesha.nfsd-4274[cache_lru] lru_run :INODE LRU :DEBUG :FD count is 0 and low >> water mark is 2048: not reaping. >> >> >> Can someone please explain what could be possible reason? >> >> Thanks, >> Supriti >> >> >> -- >> >> >> Supriti Singh >> >> >> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, >> >> >> HRB 21284 (AG Nürnberg) >> >> >> >> >> Virus-free. www.avast.com <http://www.avast.com> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Nfs-ganesha-devel mailing list >> Nfs-ganesha-devel@lists.sourceforge.net > <mailto:Nfs-ganesha-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel >> > > -- > Matt Benjamin > Red Hat, Inc. > 315 West Huron Street, Suite 140A > Ann Arbor, Michigan 48103 > > http://www.redhat.com/en/technologies/storage > > tel. 734-821-5101 > fax. 734-769-8938 > cel. 734-216-5309 > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=icon> > Virus-free. www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=emailclient_term=link> > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > > --- -> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Mount connection timeout
Is there a way to debug it further? It happens most of the time when I restart the nfs-ganesha service. The first mount command returns timeout. When I reissue the command, it works. -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) >>> Matt Benjamin <mbenja...@redhat.com> 06/19/17 9:42 PM >>> yeah - Original Message - > From: "Frank Filz" <ffilz...@mindspring.com> > To: "Supriti Singh" <supriti.si...@suse.com>, > nfs-ganesha-devel@lists.sourceforge.net > Sent: Monday, June 19, 2017 9:46:32 AM > Subject: Re: [Nfs-ganesha-devel] Mount connection timeout > > > > That’s just LRU running and not finding any work to do. I’m not sure those > messages should be LogDebug, maybe they should be LogFullDebug. > > > > Frank > > > > > From: Supriti Singh [mailto:supriti.si...@suse.com] > Sent: Monday, June 19, 2017 4:47 AM > To: nfs-ganesha-devel@lists.sourceforge.net > Subject: [Nfs-ganesha-devel] Mount connection timeout > > > > > I am using nfs-ganesha v2.5-final + CephFS FSAL. I have noticed that when I > mount, sometimes first mount attempt fails with connection time out. And it > succeed in later attempts. > > In event of timeout, the log contains the following lines many times: > > ganesha.nfsd-4274[cache_lru] lru_run :INODE LRU :DEBUG :After work, > open_fd_count:0 count:5 fdrate:1 threadwait=90 > ganesha.nfsd-4274[cache_lru] lru_run :INODE LRU :DEBUG :FD count is 0 and low > water mark is 2048: not reaping. > > > Can someone please explain what could be possible reason? > > Thanks, > Supriti > > > -- > > > Supriti Singh > > > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > > > HRB 21284 (AG Nürnberg) > > > > > Virus-free. www.avast.com > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Matt Benjamin Red Hat, Inc. 315 West Huron Street, Suite 140A Ann Arbor, Michigan 48103 http://www.redhat.com/en/technologies/storage tel. 734-821-5101 fax. 734-769-8938 cel. 734-216-5309 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] Mount connection timeout
I am using nfs-ganesha v2.5-final + CephFS FSAL. I have noticed that when I mount, sometimes first mount attempt fails with connection time out. And it succeed in later attempts. In event of timeout, the log contains the following lines many times: ganesha.nfsd-4274[cache_lru] lru_run :INODE LRU :DEBUG :After work, open_fd_count:0 count:5 fdrate:1 threadwait=90 ganesha.nfsd-4274[cache_lru] lru_run :INODE LRU :DEBUG :FD count is 0 and low water mark is 2048: not reaping. Can someone please explain what could be possible reason? Thanks, Supriti -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Systemd service file
It seems my spec file was not correct. Hence, nfs-ganesha service was not getting installed as ganesha at /etc/sysconfig. It was a bit confusing because of two different names: nfs-ganesha and ganesha. -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) >>> Daniel Gryniewicz <d...@redhat.com> 05/05/17 9:25 PM >>> FWIW, we should probably rename scrips/sysconfig/nfs-ganesha to scripts/sysconfig/ganesha, since the .spec file renames it on install, and it bit someone here trying to generate .debs. Daniel On 05/05/2017 10:44 AM, Soumya Koduri wrote: > > > On 05/05/2017 07:04 PM, Supriti Singh wrote: >> Hello, >> >> In the file scripts/systemd/nfs-ganesh.service the EnviromentFile >> expected is named "ganesha". But the file in systemd/sysconfig is named >> "nfs-ganesha". Is it intentional? >> > > yes. That file gets generated at runtime by nfs-ganesha-config.service > -> /usr/libexec/ganesha/nfs-ganesha-config.sh > > Thanks, > Soumya > >> Thanks, >> Supriti >> >> -- >> Supriti Singh >> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, >> HRB 21284 (AG Nürnberg) >> >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >> >> >> ___ >> Nfs-ganesha-devel mailing list >> Nfs-ganesha-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel >> > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Readdir with nfs4err_serverfault
Hi Daniel, Like you said, only if junction is a directory, callback getattrs is called. Which means that file type is directory. In mdcache_getattrs(), call to mdcache_refattrs() returns NO_FILE_TYPE. To me it seems like in between call from nfs_export_get_root_entry() and mdcache_refattrs(), somehow mdcache is updated. But I am not sure how. On Thu, Mar 2, 2017 at 6:12 PM, Daniel Gryniewicz <d...@redhat.com> wrote: > I don't think it's the check for type==DIRECTORY. If that fails, you'll > get the error message "Failed to get root for..." which is not in the > log snippet. The callback is only called if the getattrs() on the > junction obj succeeds, so maybe it's failing? A reproducer would help a > lot, if that's possible. > > Daniel > > On 03/02/2017 10:54 AM, Supriti Singh wrote: > > Thanks for reply. > > > > I investigated further and looking at log it seems that error occurs > > only at Junction point somehow. > > > > /*nfs4_readdir_callback :EXPORT :DEBUG :Need to cross junction to > > Export_Id 1 Path / > > */ > > /**/ > > /*nfs4_readdir_callback :RW LOCK :F_DBG :Unlocked 0x1f8ec08 > > (>state_hdl->state_lock) at /Protocols/NFS/nfs4_op_readdir.c:256 > > populate_dirent :RW LOCK :F_DBG :Got read lock on 0x1f8ec08 > > (>state_hdl->state_lock) at /FSAL/fsal_helper.c:1330 > > populate_dirent :RW LOCK :F_DBG :Unlocked 0x1f8ec08 > > (>state_hdl->state_lock) at /FSAL/fsal_helper.c:1341 > > nfs_export_get_root_entry :RW LOCK :F_DBG :Got read lock on 0x1ed6d00 > > (>lock) at support/exports.c:2118 > > nfs_export_get_root_entry :RW LOCK :F_DBG :Unlocked 0x1ed6d00 > > (>lock) at support/exports.c:2123 > > mdcache_getattrs :RW LOCK :F_DBG :Got read lock on 0x1f64680 > > (>attr_lock) at > > /FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_handle.c:979 > > mdcache_getattrs :RW LOCK :F_DBG :Unlocked 0x1f64680 (>attr_lock) > > at /FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_handle.c:1026 > > mdcache_getattrs :INODE :F_DBG :attrs obj attributes Mask = 0005dfce > > NO_FILE_TYPE > > > > */In function populate_dirent --> call to nfs_export_get_root_entry > > checks that the junction mount is a directory. > > Only if its a directory call is made to mdcache_getattrs. > > I guess somehow in mdcache_refattrs, we get the wrong FILE TYPE. > > > > But sadly I don't have a reproducer. I will try to write a script that > > can reproduce it. > > > > Thanks, > > Supriti > > > > > > -- > > Supriti Singh > > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > > HRB 21284 (AG Nürnberg) > > > >>>> Daniel Gryniewicz <d...@redhat.com> 03/02/17 2:29 PM >>> > > That's much better. A few fixes have gone in since 2.4.1 relating to > > readdir, mostly relating to large directories, or concurrent access from > > multiple clients, or readdir in the presence of add/delete/rename that > > turned up during stress testing for RHGS. It might be worth it to > > attempt to recreate on 2.4.3, and see if those fixes helped. > > > > There's also quite a bit of work that has gone into 2.5-dev related to > > cephfs, so that may have fixed issues here. Unfortunately, 2.5 isn't > > released yet; it will be at least a few weeks before that is ready. But > > if the issue can be reproduced in a lab, then checking with 2.5 may be a > > useful data point as well. > > > > Daniel > > > > On 03/01/2017 04:12 AM, Supriti Singh wrote: > >> My mistake. The package corresponds to tag 2.4.1. > >> > >> > >> -- > >> Supriti Singh > >> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > >> HRB 21284 (AG Nürnberg) > >> > >>>>> Daniel Gryniewicz <d...@redhat.com> 02/28/17 7:13 PM >>> > >> Okay, that's a very old tag, and lots of changes have gone in since. We > >> won't be able to easily nail down what changed, but -dev27 isn't > >> necessarily expected to work properly. > >> > >> Daniel > >> > >> On 02/28/2017 01:06 PM, Supriti Singh wrote: > >>> This package was created from the tag 2.4-dev-27. > >>> > >>> > >>> > >>> -- > >>> Supriti Singh > >>> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > >>> HRB 21284 (AG Nürnberg) > >>> > >>>>>> Daniel Gryniewicz <d...@redhat.com> 02/28/17 6:44 PM >>> > >>> Which exact version
Re: [Nfs-ganesha-devel] conf call beeping
I guess it was me who was causing beep in the last call. Like Kaleb, I was also trying to connect to 5695731261 using my iphone app. And dialing into 373354489/6397 from the same app, solved the issue. So, it seems 5695731261 is the culprit here. -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) >>> "Frank Filz" <ffilz...@mindspring.com> 03/08/17 7:06 PM >>> > On 03/08/2017 11:35 AM, Daniel Gryniewicz wrote: > > Firefox works if you have a new enough version (I use 50.1.0, but > > supposedly 50.x or higher works). Alternatively, chrome works. > > > > On Tue, Mar 7, 2017 at 3:45 PM, Frank Filz <ff...@redhat.com> wrote: > >> On 03/07/2017 08:46 AM, LUCAS Patrice wrote: > >>> Hi everybody, > >>> > >>> > >>> We really need to find who is beeping by trying to connect to the > >>> conf call. It's really impossible to hear or understand something by > >>> phone with this beep. > >>> > >>> > >>> Regards, > >>> > >> It seems like folks trying to connect via dial in may be the cause of > >> the beeping issues. > > Who else causes it? I didn't dial in yesterday, so if it happened yesterday > then someone else was the culprit. > > When I was the culprit, I used the Mac app and was connecting to > 5695731261. Using the same Mac, same app, dialing into 373354489/6397 > didn't cause it. Yea, I wonder if using 5695731261 is the culprit... Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Readdir with nfs4err_serverfault
Thanks for reply. I investigated further and looking at log it seems that error occurs only at Junction point somehow. nfs4_readdir_callback :EXPORT :DEBUG :Need to cross junction to Export_Id 1 Path / nfs4_readdir_callback :RW LOCK :F_DBG :Unlocked 0x1f8ec08 (>state_hdl->state_lock) at /Protocols/NFS/nfs4_op_readdir.c:256 populate_dirent :RW LOCK :F_DBG :Got read lock on 0x1f8ec08 (>state_hdl->state_lock) at /FSAL/fsal_helper.c:1330 populate_dirent :RW LOCK :F_DBG :Unlocked 0x1f8ec08 (>state_hdl->state_lock) at /FSAL/fsal_helper.c:1341 nfs_export_get_root_entry :RW LOCK :F_DBG :Got read lock on 0x1ed6d00 (>lock) at support/exports.c:2118 nfs_export_get_root_entry :RW LOCK :F_DBG :Unlocked 0x1ed6d00 (>lock) at support/exports.c:2123 mdcache_getattrs :RW LOCK :F_DBG :Got read lock on 0x1f64680 (>attr_lock) at /FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_handle.c:979 mdcache_getattrs :RW LOCK :F_DBG :Unlocked 0x1f64680 (>attr_lock) at /FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_handle.c:1026 mdcache_getattrs :INODE :F_DBG :attrs obj attributes Mask = 0005dfce NO_FILE_TYPE In function populate_dirent --> call to nfs_export_get_root_entry checks that the junction mount is a directory. Only if its a directory call is made to mdcache_getattrs. I guess somehow in mdcache_refattrs, we get the wrong FILE TYPE. But sadly I don't have a reproducer. I will try to write a script that can reproduce it. Thanks, Supriti -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) >>> Daniel Gryniewicz <d...@redhat.com> 03/02/17 2:29 PM >>> That's much better. A few fixes have gone in since 2.4.1 relating to readdir, mostly relating to large directories, or concurrent access from multiple clients, or readdir in the presence of add/delete/rename that turned up during stress testing for RHGS. It might be worth it to attempt to recreate on 2.4.3, and see if those fixes helped. There's also quite a bit of work that has gone into 2.5-dev related to cephfs, so that may have fixed issues here. Unfortunately, 2.5 isn't released yet; it will be at least a few weeks before that is ready. But if the issue can be reproduced in a lab, then checking with 2.5 may be a useful data point as well. Daniel On 03/01/2017 04:12 AM, Supriti Singh wrote: > My mistake. The package corresponds to tag 2.4.1. > > > -- > Supriti Singh > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > >>>> Daniel Gryniewicz <d...@redhat.com> 02/28/17 7:13 PM >>> > Okay, that's a very old tag, and lots of changes have gone in since. We > won't be able to easily nail down what changed, but -dev27 isn't > necessarily expected to work properly. > > Daniel > > On 02/28/2017 01:06 PM, Supriti Singh wrote: >> This package was created from the tag 2.4-dev-27. >> >> >> >> -- >> Supriti Singh >> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, >> HRB 21284 (AG Nürnberg) >> >>>>> Daniel Gryniewicz <d...@redhat.com> 02/28/17 6:44 PM >>> >> Which exact version of 2.4 are they using? If it's 2.4.0.3 or earlier, >> then attribute access was reworked in 2.4.0.4 to fix a lot of races. >> >> Daniel >> >> On 02/28/2017 12:18 PM, Supriti Singh wrote: >>> Hello All, >>> >>> For one of our client, using nfs-ganesha v2.4 and ceph v10.2.4, readdir >>> fails with error: >>> >>> On nfs-client: "/*Remote I/O error*/" >>> >>> In nfs-ganesha server log (Removed some part of readability) >>> >>> */mdcache_readdir :NFS READDIR :F_DBG :About to readdir in >>> mdcache_readdir: directory=0x1f8dc10 cookie=0 collisions 0 >>> mdcache_getattrs :INODE :F_DBG :attrs obj attributes Mask = 0005dfce >>> NO_FILE_TYPE >>> Encode FAILED for attr 1, name = FATTR4_TYPE >>> NFS READDIR :F_DBG :Returning NFS4ERR_SERVERFAULT /* >>> >>> >>> But for the same directory=0x1f8dc10 , readdir works sometime. >>> In >>> :F_DBG :Encoded attr 1, name = FATTR4_TYPE*/" >>> >>> Could there be a possible race condition somewhere in accessing mdcache, >>> because of which for the same directory it works sometime? >>> >>> I have not been able to reproduce it. Looking at code, it seems somehow >>> mdcache and attributes are not in sync. >>> Client is also using cephfs cache tiering, but I think that should not >>> have any effect on nfs-ganesha mdcache. >>> >>> Any hints on how to debug it further? >>> >>> Thanks
[Nfs-ganesha-devel] pNFS with CephFS and RGW
Hi, Is it possible to use pNFS protocol for CephFS and RGW FSAL? If yes, how to specify it in the config file? I could not find any documentation regarding the same. Thanks, Supriti -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
Re: [Nfs-ganesha-devel] Readdir with nfs4err_serverfault
This package was created from the tag 2.4-dev-27. -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) >>> Daniel Gryniewicz <d...@redhat.com> 02/28/17 6:44 PM >>> Which exact version of 2.4 are they using? If it's 2.4.0.3 or earlier, then attribute access was reworked in 2.4.0.4 to fix a lot of races. Daniel On 02/28/2017 12:18 PM, Supriti Singh wrote: > Hello All, > > For one of our client, using nfs-ganesha v2.4 and ceph v10.2.4, readdir > fails with error: > > On nfs-client: "/*Remote I/O error*/" > > In nfs-ganesha server log (Removed some part of readability) > > */mdcache_readdir :NFS READDIR :F_DBG :About to readdir in > mdcache_readdir: directory=0x1f8dc10 cookie=0 collisions 0 > mdcache_getattrs :INODE :F_DBG :attrs obj attributes Mask = 0005dfce > NO_FILE_TYPE > Encode FAILED for attr 1, name = FATTR4_TYPE > NFS READDIR :F_DBG :Returning NFS4ERR_SERVERFAULT /* > > > But for the same directory=0x1f8dc10 , readdir works sometime. > In the log, it prints the correct attr "/*nfs4_FSALattr_To_Fattr :NFS4 > :F_DBG :Encoded attr 1, name = FATTR4_TYPE*/" > > Could there be a possible race condition somewhere in accessing mdcache, > because of which for the same directory it works sometime? > > I have not been able to reproduce it. Looking at code, it seems somehow > mdcache and attributes are not in sync. > Client is also using cephfs cache tiering, but I think that should not > have any effect on nfs-ganesha mdcache. > > Any hints on how to debug it further? > > Thanks, > Supriti > > -- > Supriti Singh > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > > ___ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
[Nfs-ganesha-devel] Readdir with nfs4err_serverfault
Hello All, For one of our client, using nfs-ganesha v2.4 and ceph v10.2.4, readdir fails with error: On nfs-client: "Remote I/O error" In nfs-ganesha server log (Removed some part of readability) mdcache_readdir :NFS READDIR :F_DBG :About to readdir in mdcache_readdir: directory=0x1f8dc10 cookie=0 collisions 0 mdcache_getattrs :INODE :F_DBG :attrs obj attributes Mask = 0005dfce NO_FILE_TYPE Encode FAILED for attr 1, name = FATTR4_TYPE NFS READDIR :F_DBG :Returning NFS4ERR_SERVERFAULT But for the same directory=0x1f8dc10 , readdir works sometime. In the log, it prints the correct attr "nfs4_FSALattr_To_Fattr :NFS4 :F_DBG :Encoded attr 1, name = FATTR4_TYPE" Could there be a possible race condition somewhere in accessing mdcache, because of which for the same directory it works sometime? I have not been able to reproduce it. Looking at code, it seems somehow mdcache and attributes are not in sync. Client is also using cephfs cache tiering, but I think that should not have any effect on nfs-ganesha mdcache. Any hints on how to debug it further? Thanks, Supriti -- Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N��rnberg) -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
