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
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
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 02/28/17 6:44 PM >>>
Which exact version of 2.4 are they using? If it's 2.4.0.3
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.
>
>
>
>
At Connectathon, Synopsis is running their fuzz tests against Ganesha. One
issue that has arose is how Ganesha manages the /var/lib/nfs/ganesha/v4recov
directory on startup after their tests created some 65k clientids. It seems
like Ganesha just wedges on startup...
Frank
---
This email has
>From :
ka...@redhat.com has uploaded a new change for review. (
https://review.gerrithub.io/350953
Change subject: nfs-ganesha.spec: need selinux tools for minimalist installs
..
nfs-ganesha.spec: need
Hello Developers
we have two servers with NFS active/active Ganesha running, each server has 4
vlan IPs say of (192.168.1. 192.168.2. 192.168.3. 192.168.4.) can this be
binded binded with NFS service
is this feature can be supported by ganesha ?
Hi everybody,
The last gerrithub submitted version of the set of commits that implements
FSAL_PROXY support_ex is now a complete one and is passing CTHON basic,
general, lock and special.
For FSAL_PROXY, the next two steps is first to move from v4 to v4.1 protocol,
and then to really store