I did update submodules but did not installed the libntirpc, where do you
get it?
Thanks, Marc.
From: Malahal Naineni
To: Marc Eshel
Cc: Frank Filz ,
nfs-ganesha-devel@lists.sourceforge.net
Date: 11/14/2017 11:37 AM
Subject:Re: [Nfs-ganesha-devel] Announce Push of V2.6
I skipped a couple of dev releases but now I am get this when I try to
mount.
(gdb) c
Continuing.
[New Thread 0x71b3b700 (LWP 18716)]
[New Thread 0x7ffe411ce700 (LWP 18717)]
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x71b3b700 (LWP 18716)]
0x75e13989 in __GI_
Sorry, the problem is gone after reboot.
Thanks, Marc.
From: William Allen Simpson
To: Marc Eshel , Frank Filz
Cc: nfs-ganesha-devel@lists.sourceforge.net
Date: 09/20/2017 03:39 PM
Subject:Re: [Nfs-ganesha-devel] Announce Push of V2.6-dev.10
It's harder, as
Just update to V2.6-dev.10 after skipping couple of version and can not
mount and I see this msg in the log.
20/09/2017 10:52:30 : epoch 59c2aac5 : bear105 :
ganesha.nfsd-25633[0x7f7a81da1ee0] rpc :TIRPC :EVENT :svc_vc_recv:
0x7f7a6c000ab0 fd 18 recv errno 0 (will set dead)
Marc.
From: "F
Can you also add, it is a minor change in the value of
FATTR4_XATTR_SUPPORT
Thanks, Marc.
commit ac16ad42a514de218debc9b21e92cf9ca353ccc4
Author: Marc Eshel
Date: Sun Jul 30 12:50:14 2017 -0700
update FATTR4_XATTR_SUPPORT
update FATTR4_XATTR_SUPPORT to 82 based on latest
draft
Another bug that was just introduced on the up call path, this time op_ctx
is good but op_ctx->ctx_export is null.
Marc.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fba8356b280 (LWP 10471)]
0x0053eb6e in mdc_check_mapping (entry=0x7fb874001480) at
/nas/ga
Frank,
Do I have to re-post my patches or can they go into rc5 ?
Marc.
From: "Frank Filz"
To:
Date: 05/05/2017 04:47 PM
Subject:[Nfs-ganesha-devel] Announce Push of V2.5-rc4
Branch next
Tag:V2.5-rc4
NOTE: This merge has an ntirpc pullup - please update your submodule
Rele
Hi Frank,
You recently added
commit 65599c645a81edbe8b953cc29ac29978671a11be
Author: Frank S. Filz
Date: Wed Mar 1 17:28:18 2017 -0800
Fill in FATTR4_SUPPORTED_ATTRS from FSAL fs_supported_attrs
but when posix2fsal_attributes() is called from the up thread op_ctx is
null.
Program rec
GPFS has few 2.4 functions implemented including SEEK.
Marc.
From: Frank Filz
To: patrice.lu...@cea.fr
Cc: MARTINET Dominique ,
nfs-ganesha-devel@lists.sourceforge.net, LEIBOVICI Thomas
, DENIEL Philippe 158570
Date: 02/16/2017 10:54 AM
Subject:Re: [Nfs-ganesha-devel] see
I am trying to update the gpfs.h but since it is not complying with
Ganesha format it is rejected. I have to keep it the same as the one used
by GPFS source code, is there a way to force it in?
Thanks, Marc.
--
Check ou
I see that this mailing list will not let you share attachments.
Marc.
From: Marc Eshel/Almaden/IBM@IBMUS
To: "Kaleb S. KEITHLEY"
Cc: nfs-ganesha-devel@lists.sourceforge.net
Date: 02/07/2017 10:45 AM
Subject:Re: [Nfs-ganesha-devel] Fwd: Ganesha logo / hex sticker
I could not see you logo for some reason it got detached but here is the
one I used when I worked on Ganesha.
From: "Kaleb S. KEITHLEY"
To: nfs-ganesha-devel@lists.sourceforge.net
Date: 02/07/2017 08:38 AM
Subject:[Nfs-ganesha-devel] Fwd: Ganesha logo / hex sticker
---
Can someone answer few questions about RDMA?
Which Ganesha version supports RDMA, with which hardware, NFS protocols,
and FSALs?
Thanks, Marc.
--
Check out the vibrant tech community on one of the world's most
engagin
Not sure I follow, but yes it fixed my problem.
Thanks, Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS,
Cc:
Date: 10/28/2016 10:47 AM
Subject:RE: [Nfs-ganesha-devel] Announce Push of V2.4.0.4
Ok, I just tried NSF v3, and discovered Ganesha wasn
Re: [Nfs-ganesha-devel] Announce Push of V2.4.0.4
On 10/27/2016 08:58 PM, Marc Eshel wrote:
> Hi Frank,
> I see two problems with this version.
> 1. It looks like I can not use NFSv3 mount.
> 2. if I export the root of the GPFS fs the export create gets and error
I
> be
Hi Frank,
I see two problems with this version.
1. It looks like I can not use NFSv3 mount.
2. if I export the root of the GPFS fs the export create gets and error I
believe because of the
971670b6df6546360514b8ecb50bc0db843b39d6 patch to ensure that a handle has
a
parent pointer, which is tryi
Cc: Malahal Naineni/Beaverton/IBM@IBMUS, dhil...@us.ibm.com,
fschm...@us.ibm.com, gfsch...@us.ibm.com, Marc Eshel/Almaden/IBM@IBMUS,
robg...@us.ibm.com
Date: 10/20/2016 05:32 PM
Subject:Re: nfs testing for SAP - status - new traces / new
approach
marc will send a email on what i
I am a little confused, can you end up with 2 objects if you use openat()
like FSAL_VFS does?
Why does FSAL_VFS has a merge() method implementation.
If I change FSAL_GPFS to use openat() do I need to implement merge() ?
Marc.
From: "Frank Filz"
To: "'nfs-ganesha-devel'"
Date: 09/22/2
Hi Frank,
pNFS seems to work for some basic tests.
Thanks, Marc.
From: "Frank Filz"
To: "'nfs-ganesha-devel'"
Date: 09/21/2016 03:14 PM
Subject:[Nfs-ganesha-devel] Announce Push of V2.4-rc7
Branch next
Tag:V2.4-rc7
NOTE: This is the final merge before 2.4.0 baring some sho
Hi Frank,
Are you going to push the patch you asked me to test ?
Thanks, Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: "'nfs-ganesha-devel'"
Date: 09/07/2016 04:18 PM
Subject:RE: [Nfs-ganesha-devel] NLM async locking
I c
Ye, FSAL_GPFS could use openat but I want to have control over all the
calls in GPFS before it calls the VFS. Do you see any problem with the
code?
Thanks, Marc.
From: "Frank Filz"
To: "'nfs-ganesha-devel'" ,
Marc Eshel/Almaden/IBM@IBMUS
Date:
I see, I tried your fix and it did work for the case that I had problems
with.
Thanks, Marc.
From: Frank Filz
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: nfs-ganesha-devel
Date: 09/07/2016 09:14 PM
Subject:Re: [Nfs-ganesha-devel] NLM async locking
Request is resubmitted to
It will not help if the request is not resubmitted to the FSAL.
Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: "'nfs-ganesha-devel'"
Date: 09/07/2016 04:18 PM
Subject:RE: [Nfs-ganesha-devel] NLM async locking
I changed it so
Just looking at the code I don't see where you retry the lock request from
the FSAL which is required to add it back to the FSAL queue.
Am I missing something?
Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: "'nfs-ganesha-devel'"
Did you get a chance to look at this problem?
Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: "'nfs-ganesha-devel'"
Date: 08/29/2016 02:37 PM
Subject:RE: NLM async locking
> I see the following failure:
> 1. Get conflict
FSAL_{CEPH,GLUSTER}: #include "config.h" to get
LINUX
a0aa7e4 Marc Eshel GPFS_FSAL: fix few CIDs
a1813e9 Marc Eshel FSAL_GPFS: more fixes and cleanup for multi-fd
7f82e3e Malahal Naineni GPFS: remove unused code
d9dc8eb Malahal Naineni Make sure that netgroup cache entry exists before
removi
I can look at your fix but the problem here has nothing to do with cancel.
This locks should work without client involvement.
Can you point me again to ganltc.
Marc.
From: Malahal Naineni
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: Frank Filz , nfs-ganesha-devel
Date: 08/29/2016 06:25
Hi Frank,
I see the following failure:
1. Get conflicting locks from 3 clients
cli 1 gets 0-100
cli 2 is blocked on 0-1000
cli 3 is blocked on 0-1
2. cli 1 unlocks
up-call for cli 2 and 3 to retry
cli 2 gets 0-1000
cli 3 is blocked on 0-1000
3. cli 2 unlocks
up-cal
Please merge them, I will do more testing next week.
Thanks, Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: "'NFS Ganesha Developers'"
Date: 08/26/2016 09:58 AM
Subject:RE: Change in ffilz/nfs-ganesha[next]: Add blocking lock
"Frank Filz" wrote on 08/25/2016 02:23:39 PM:
> From: "Frank Filz"
> To: Marc Eshel/Almaden/IBM@IBMUS
> Cc: "'NFS Ganesha Developers'"
> Date: 08/25/2016 02:23 PM
> Subject: RE: Change in ffilz/nfs-ganesha[next]: Add blocking locks
>
"Frank Filz" wrote on 08/25/2016 11:48:45 AM:
> From: "Frank Filz"
> To: Marc Eshel/Almaden/IBM@IBMUS
> Cc: "'NFS Ganesha Developers'"
> Date: 08/25/2016 11:49 AM
> Subject: RE: Change in ffilz/nfs-ganesha[next]: Add blocking locks
> t
"Frank Filz" wrote on 08/25/2016 11:01:37 AM:
> From: "Frank Filz"
> To: Marc Eshel/Almaden/IBM@IBMUS
> Cc: "'NFS Ganesha Developers'"
> Date: 08/25/2016 11:01 AM
> Subject: RE: Change in ffilz/nfs-ganesha[next]: Add blocking locks
&
Hi Frank,
I am not sure of the logic in this section of code in FSAL/commonlib.c
fsal_find_fd()
but the lock fails because the openflags is zero before and after the &
FSAL_O_RDWR;
The lock is write lock and the open was not done for write.
If I change it to openflags = related_fd->openflags |
This time it did work.
Marc.
From: Daniel Gryniewicz
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: Frank Filz , NFS Ganesha Developers
Date: 08/21/2016 02:45 PM
Subject:Re: MDC up call
In general, MDCACHE assumes it has op_ctx set, and I'd prefer to not
have that assum
READ_MUTEX_unlock(&state->state_mutex);
PTHREAD_RWLOCK_unlock(&export->lock);
put_gsh_export(export);
From: Marc Eshel/Almaden/IBM@IBMUS
To: "Frank Filz"
Cc: nfs-ganesha-devel@lists.sourceforge.net
Date: 08/18/2016 09:21 AM
Subject:Re: [Nfs-ganesha-devel] multi fd
I am not sure you need to set op_ctx
I fixed it for this path by not calling mdc_check_mapping() from
mdcache_find_keyed() if op_ctx is NULL
I think the mapping should already exist for calls that are coming from
up-call.
Marc.
From: Daniel Gryniewicz
To: Marc Eshel/Almaden/IBM@IBMUS
arg=0x7f45240009d0) at
/nas/ganesha/new-ganesha/src/support/fridgethr.c:550
#3 0x7f46c4731df3 in start_thread (arg=0x7f44dbfff700) at
pthread_create.c:308
#4 0x7f46c3df13dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113
From: Daniel Gryniewicz
To: Marc Eshel/Alma
uct mdcache_fsal_export *export = mdc_cur_export();
(gdb) p op_ctx
$1 = (struct req_op_context *) 0x0
From: Marc Eshel/Almaden/IBM@IBMUS
To: "Frank Filz"
Cc: nfs-ganesha-devel@lists.sourceforge.net
Date: 08/18/2016 09:21 AM
Subject:Re: [Nfs-ganesha-devel] multi fd support
is wrong.
Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc:
Date: 08/17/2016 10:04 PM
Subject:RE: multi fd support
> Hi Frank,
> Don't we need fsal_close() to call close2() ?
> We need the owner so we can release only the locks for thi
Hi Frank,
Don't we need fsal_close() to call close2() ?
We need the owner so we can release only the locks for this fd before
closing it.
Marc.
--
___
Nfs-ganesha-devel mailing
A common reason to update the exports is for adding and removing NFS
clients, is that covered ?
Marc.
From: Kaleb KEITHLEY
To: Frank Filz , "'nfs-ganesha-devel'"
Date: 08/10/2016 01:40 PM
Subject:Re: [Nfs-ganesha-devel] Addtional parameters that might be
interesting to dynam
ps reference to object
*/
void handle_ops_pnfs(struct fsal_obj_ops *ops)
{
ops->layoutget = layoutget;
ops->layoutreturn = layoutreturn;
ops->layoutcommit = layoutcommit;
}
From: Daniel Gryniewicz
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: Frank Filz ,
nfs-gane
Do we have an FSAL that implemented multi-fd ?
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc:
Date: 07/25/2016 04:10 PM
Subject:RE: multi-fd
> Why do we have reopen2 as one of the multi-fd support, I thought that
one
> of the resones for m
Hi Frank,
Why do we have reopen2 as one of the multi-fd support, I thought that one
of the reasons for multi fd is so we don't have to reopen files when we
get different/conflicting open options.
Do we have an FSAL that implemented multi-fd?
Marc.
Hi Frank,
Why do we have reopen2 as one of the multi-fd support, I thought that one
of the resones for multi fd is so we don't have to reopen files when we
get differnet/conflicting open options.
Marc.
From: GerritHub
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: CEA-HPC , Matt Ben
nce to object
*/
void handle_ops_pnfs(struct fsal_obj_ops *ops)
{
ops->layoutget = layoutget;
ops->layoutreturn = layoutreturn;
ops->layoutcommit = layoutcommit;
}
From: Marc Eshel/Almaden/IBM
To: Marc Eshel/Almaden/IBM@IBMUS, d...@redhat.com
Cc: &q
,
struct fsal_layoutget_res *res)
{
return NFS4ERR_LAYOUTUNAVAILABLE;
}
From: Marc Eshel/Almaden/IBM
To: Marc Eshel/Almaden/IBM@IBMUS, d...@redhat.com
Cc: "Frank Filz" ,
nfs-ganesha-devel@lists.sourceforge.net
Date: 07/23/2016 09:25 PM
Subject:FSAL_M
gments(op_ctx->fsal_export);
if (max_segment_count == 0) {
LogWarn(COMPONENT_PNFS,
"The FSAL must specify a non-zero
fs_maximum_segments.");
nfs_status = NFS4ERR_LAYOUTUNAVAILABLE;
goto out;
}
ghts
* A variety of small fixes
* RGW: Add 3 new config options
Signed-off-by: Frank S. Filz
Contents:
5ba03b2 Frank S. Filz V2.4-dev-26
77c71ae Marc Eshel GPFS_FSAL: Use a shorter file handle.
a910381 Swen Schillig [valgrind] memory leak in mdcache_exp_release()
1c45f6a Matt Benjamin r
I don't know how the new FSAL_MDCACHE is working but it is calling the
default operation instead of the real FSAL export and calling the encoding
fs_layouttypes()
Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc:
Date: 07/15/2016 04:43 PM
Subject:
It looks like we are not telling the NFS client that we support pNFS, I
don't see a call to encode_fs_layout_types()
[FATTR4_FS_LAYOUT_TYPES] = {
.name = "FATTR4_FS_LAYOUT_TYPES",
.supported = 1,
.size_fattr4 = sizeof(fattr4_fs_layout_types
ot; OFF)
option(USE_FSAL_GLUSTER "build GLUSTER FSAL shared library" ON)
option(USE_FSAL_NULL "build NULL FSAL shared library" ON)
option(USE_FSAL_RGW "build RGW FSAL shared library" OFF)
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc:
[ 91%] Building C object
FSAL/FSAL_VFS/panfs/CMakeFiles/fsalpanfs.dir/handle.c.o
/nas/ganesha/new-ganesha/src/FSAL/FSAL_VFS/panfs/handle.c: In function ‘
panfs_getattrs’:
/nas/ganesha/new-ganesha/src/FSAL/FSAL_VFS/panfs/handle.c:42:36: error: ‘
struct vfs_fsal_obj_handle’ has no member named ‘attr
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: , "'Niels de Vos'"
, "'NFS Ganesha Developers'"
Date: 06/21/2016 12:40 PM
Subject:RE: [Nfs-ganesha-devel] no_subtree_check option
> Does Ganesha have something
Change misleading subject.
From: Marc Eshel/Almaden/IBM@IBMUS
To: "Frank Filz"
Cc: "'NFS Ganesha Developers'"
, mala...@linux.vnet.ibm.com
Date: 06/21/2016 12:06 PM
Subject:Re: [Nfs-ganesha-devel] existing export modifications
withoutint
Does Ganesha have something equivalent to no_subtree_check, I am
interested in the subtree_check part, to verify that fh is not trying to
access files above the export point, like in kNFS.
Thanks, Marc.
--
Attend Shap
This version is better I am mounting v3 and I can now do ls now, but
coping a small file into the mount point I get
Marc.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f6595b0e280 (LWP 10125)]
0x00528775 in mdc_cur_export () at
/nas/ganesha/new-ganesha/src/
So this logic is already in V2.4-dev-20 for FSAL_GPFS ?
Marc.
From: Daniel Gryniewicz
To: Marc Eshel/Almaden/IBM@IBMUS, Frank Filz
Cc: "'nfs-ganesha-devel'"
Date: 06/09/2016 12:02 PM
Subject:Re: [Nfs-ganesha-devel] Posted patches that include my
c
l was not
passing a full fh it is passing a key that the old code used to use for a
look-up of the full fh in the cache_entry_t and used that full fh to
recall delegation from the NFS client.
Am I missing something?
Thanks, Marc.
From: "Frank Filz"
To: Marc Eshel/Almad
FSAL_GPFS is not working I belive that get_ref is null, it crashes on the
2nd mount.
fsal_status_t nfs_export_get_root_entry(struct gsh_export *export,
struct fsal_obj_handle **obj)
{
PTHREAD_RWLOCK_rdlock(&export->lock);
if (export->exp_r
So it sound like you prefer config re-reading, is it possible to do it
with a clear specification of what will be updated at this time and over
time we can add attributes that can be changed?
Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: ,
, Sven Oehme/A
We need add/delete individual clients for sure but we also need the
ability to change netgroups.
Another requirement is to switch export to or from ro/rw which should not
be to complicated.
Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS,
Cc: , Sven
Oehme/A
Yes, I think that re-reading the config file might be to complicated, lets
compile a list of the attributes that we must be able to change and than
decide on the best way to do it.
Marc.
From: mala...@linux.vnet.ibm.com
To: Frank Filz
Cc: Marc Eshel/Almaden/IBM@IBMUS,
nfs-ganesha
Hi Frank,
We have some critical attributes of export that we need to change
dynamically with out restarting Ganesha. Do you or anyone else remember
why we decided it was difficult to support change export? are there some
specific attributes that are difficult to change and some that can be
eas
Hi Frank,
Congratulation!
I can fix WARNING: line over 80 characters
but the error with the missing (void) I am just following existing
practice should I change it?
- Forwarded by Marc Eshel/Almaden/IBM on 12/02/2015 05:19 PM -
From: GerritHub
To: Marc Eshel/Almaden/IBM
change until we have solutions for all other issues
that where discussed.
Marc.
From: mala...@linux.vnet.ibm.com
To: Marc Eshel/Almaden/IBM@IBMUS
Cc: Frank Filz ,
nfs-ganesha-devel@lists.sourceforge.net
Date: 11/02/2015 01:24 PM
Subject:Re: [Nfs-ganesha-devel] Topic for d
abort before try to reduce the cache size.
Marc.
From: "Frank Filz"
To: Marc Eshel/Almaden/IBM@IBMUS
Cc:
Date: 11/02/2015 11:24 AM
Subject:RE: [Nfs-ganesha-devel] Topic for discussion - Out of
Memory Handling
There seems to be overwhelming support for log an
I don't believe that we need to restart Ganesha on every out of memory
calls for many reasons, but I will agree that we can have two types or
calls one that can accept no memory rc and one that terminate Ganesha if
the call is not successful.
Marc.
From: "Frank Filz"
To:
Date: 10/2
if we want to continue to support vmware we are limited to 56 bytes file
handle for NFSv3.
Marc.
From: "Frank Filz"
To: mala...@linux.vnet.ibm.com
Cc: "'NFS Ganesha Developers'"
Date: 09/23/2015 01:45 PM
Subject:Re: [Nfs-ganesha-devel] Export_id larger than 16 bits
>
Hi Frank,
The latest version of Ganesha still works fine with fs-locations, at least
with GPFS, the only thing that can be improved on is to add a check to see
if the FSAL supports fs-location in check_fs_location() before calling
fsal_obj_ops.fs_locations() which is more expensive, or add anoth
- Forwarded by Marc Eshel/Almaden/IBM on 08/27/2015 09:24 AM -
From: internet-dra...@ietf.org
To: Manoj Naik/Almaden/IBM@IBMUS, Marc Eshel/Almaden/IBM@IBMUS, Manoj
Naik/Almaden/IBM@IBMUS, Marc Eshel/Almaden/IBM@IBMUS
Date: 08/18/2015 10:09 PM
Subject:New Version
Hi Frank, Matt,
I remember we had the discussion of fd description limit but don't
remember the details.
First how do we control the limit of fd in Ganesha.
We see low performance when running with high number of open files, are
there known problems with fd management?
This is for NFSv3.
Thanks,
"Matt W. Benjamin" wrote on 07/29/2015 01:38:14 PM:
> From: "Matt W. Benjamin"
> To: Marc Eshel/Almaden/IBM@IBMUS
> Cc: "NFS Ganesha Developers (Nfs-ganesha-
> de...@lists.sourceforge.net)"
> Date: 07/29/2015 01:38 PM
> Subject: Re: inode cach
Hi Matt,
I see bad perfromance when stating milloins of files, the inode cache is
set to 1.5 million. Are there any configuration changes that I can make to
the inode cache, even code changes of some hard coded values that will
help with performance of big nuber of files?
Thanks , Marc.
EVENT_TAKE_IP is not used by cNFS right now.
From: mala...@linux.vnet.ibm.com
To: Soumya Koduri
Cc: nfs-ganesha-devel@lists.sourceforge.net
Date: 06/24/2015 06:48 AM
Subject:Re: [Nfs-ganesha-devel] 'clustered' configuration
parameter + use of nodeid
Soumya Koduri [skod
Hi Frank,
The Ganesha wiki still points to the 2.1 release.
Thanks, Marc.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Perform
76 matches
Mail list logo
