1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Standard RTEMS NFSv3 client |
From: | "Zhou, Jingchen via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Matt Rippa <mrippa at gemini.edu> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 11 Feb 2020 22:12:23 +0000 |
Hi Matt, We experienced a similar problem. Our NFS server on PROD is based on Oracle ZFS Storage system, and we had to work with Oracle to reconfigure the system to be
backward compatible with our RTEMS NFSv2 client. On DEV, we depend on afsnfs as a file server, and again we had to work with our vendor to add a software support on the server side for RTEMS NFSv2 client as well. Painful experiences.
We do not have any CentOS7 based NFS server. But I think you can configure a CentOS7 nfs server to support v2. There may be a bug on CentOS 7 NFSv2 client, as
reported, but you may have a luck with RTEMS NFSv2 client. For other relocatable projects, I tested RHEL6 and 7 based NFS server with RTEMS NFSv2 client - it worked fine.
The best is for you to consult Till Straumann to see if he can upgrade RTEMS’s NFS to v3.
Regards, Jingchen From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Matt Rippa via Tech-talk Hello EPICS/RTEMS users, Back in 2017 there were some emails in the EPICS and RTEMS community about requesting support for an RTEMS NFSv3 client . We're getting increasing requests from our IT department to support this but don't see an easy way forward. We're
running RTEMS 4.10.2 and NFSv2 is currently working and supported by default with a CentOS 6 file server. Moving to CentOS 7 we're getting push back supporting NFSv2. It's not enabled by default and we have to configure it. Our IT department believes the ability
to enable NFS v2 on CentOS7 is a bug and it may not function properly after routine maintenance on a CentOS7 machine. This may be related to [1] below. A few questions: 1. Is there any risk manually configuring a CentOS7 nfs server to use version 2 via /etc/sysconfig/nfs ?: Config changes to /etc/sysconfig/nfs: 2. Do you know if CentOS 8 continues to support NFSv2, even if you have to configure it? 3. Do you know if/when we'll hit a hard stop with NFS v2 support on CentOS? 4. Gemini may be able to find some funding for the development of an NFSv3 client on RTEMS. Are other sites interested in pursuing this and sharing the cost? Aloha, -Matt Rippa |