Hi Allesandro,
I need the following output from you,
1. After you execute ganesha.enable on command.
ps aux | grep ganesha
showmount -e localhost
cat /etc/ganesha/ganesha.conf
cat /etc/ganesha/exports/export.VOLNAME.conf or
/usr//export.VOLNAME.conf
tail /var/log/ganesha.log or wherever the
Hi Meghana,
Il giorno 18/giu/2015, alle ore 07:04, Meghana Madhusudhan
mmadh...@redhat.com ha scritto:
On 06/17/2015 10:57 PM, Alessandro De Salvo wrote:
Hi,
when disabling exports from gluster 3.7.1, by using gluster vol set volume
ganesha.enable off, I always get the following
Hi Malahal,
We are using VFS FSAL.
In the original email, I noted that the parent cache entry in question is qid
= LRU_ENTRY_CLEANUP, so I guess the cache entry is in the cleanup queue,
whereas this thread in question is trying to access the entry to fill up
some post-op attributes in the NFS
Hi Meghana,
Il giorno 18/giu/2015, alle ore 16:06, Meghana Madhusudhan
mmadh...@redhat.com ha scritto:
Hi Allesandro,
I need the following output from you,
1. After you execute ganesha.enable on command.
ps aux | grep ganesha
root 6699 94.0 1.1 953488 193272 ? Ssl Jun17
On 06/18/2015 07:55 PM, Alessandro De Salvo wrote:
Hi Meghana,
Il giorno 18/giu/2015, alle ore 16:06, Meghana Madhusudhan
mmadh...@redhat.com ha scritto:
Hi Allesandro,
I need the following output from you,
1. After you execute ganesha.enable on command.
ps aux | grep ganesha
root
On 06/18/2015 07:39 PM, Malahal Naineni wrote:
I still have not looked at the log messages, but I see the dbus thread
waiting for the upcall thread to complete when an export is removed. Is
there is a time limit on how the upcall thread gets blocked?
A variable called 'destroy_mode' is used
From Jiffin Tony Thottan jthot...@redhat.com:
Jiffin Tony Thottan has uploaded a new change for review.
https://review.gerrithub.io/236914
Change subject: FSAL_GLUSTER : clean up patch for nfs4_acl - posix_acl
conversion
..
From Jiffin Tony Thottan jthot...@redhat.com:
Jiffin Tony Thottan has uploaded a new change for review.
https://review.gerrithub.io/236924
Change subject: FSAL_GLUSTER : clean up patch for nfs4_acl - posix_acl
conversion
..
Soumya Koduri [skod...@redhat.com] wrote:
I thought pthread_exit() always returns a pointer which gets assigned to
retval of pthread_join(). I assume this is the flow --
pthread_exit() does take a void *, since it is void *, it is up to
you whether to really pass some pointer or some casted
Hi Omkar,
Controlling ganesha cache size will help decide caching of other components
running on that machine.
Also I would like to know for given X GB of cache what is the performance
and how it affects if I increase or decrease cache.
--Nilesh
On Wed, Jun 17, 2015 at 11:04 PM, Omkar Joshi
We were discussing on the concall the need to do more to control Ganesha’s
memory footprint. We limit the number of cache inode entries, but not the
number of directory entries. There are other areas we don’t place any limits on
such as number of byte range locks (imagine a process locking
interesting... Tx for more info Filz and Nilesh...
On Thu, Jun 18, 2015 at 9:53 AM, Filz, Frank ff...@panasas.com wrote:
We were discussing on the concall the need to do more to control
Ganesha’s memory footprint. We limit the number of cache inode entries, but
not the number of directory
On 06/18/2015 10:33 PM, Malahal Naineni wrote:
Soumya Koduri [skod...@redhat.com] wrote:
I thought pthread_exit() always returns a pointer which gets assigned to
retval of pthread_join(). I assume this is the flow --
pthread_exit() does take a void *, since it is void *, it is up to
you
Gerrithub has a feature to allow editing of patches. This seems like a nice
feature.
The problem is that it does not rebase any subsequent patches.
So when I merge by pulling a branch from your top patch, I DON'T get the
edited patches... Unless they ARE the top patch of a patch set (or only
14 matches
Mail list logo
