Frank Filz comments

Results 698 comments of


                                            Frank Filz

BUG: FSAL's state_free function doesn't actually free the state - was Question: Is the memory occupied by ceph_alloc_state normal?

This does impact all FSALs that implement state_free...

BUG: FSAL's state_free function doesn't actually free the state - was Question: Is the memory occupied by ceph_alloc_state normal?

> I tried the new patch, the bug seems to be fixed, memory of ganesha is stable. Thanks for the verification.

BUG: FSAL's state_free function doesn't actually free the state - was Question: Is the memory occupied by ceph_alloc_state normal?

This needs a backport to V5-stable

Q: nfs-ganesha uses a lot of wall time. If a clock jump occurs, does it affect functionality?

Bumping things that got depressed to to tagging other issues.

Q: nfs-ganesha uses a lot of wall time. If a clock jump occurs, does it affect functionality?

I don't think the patch is a good way to solve the issue. Is this still a problem and if so, can we find another solution?

How do I get the number of clients for users of nfs-ganesha's export

There may be a reasonable request here, tagging as enhancement.

Better handling of symlinks in Path=

The BUG is we need a better log message. The DOCUMENTATION is we need to document that symlinks aren't allowed in the path specified by Path=.

NFSv3 mounting failed,"RPC Error: Program unavailable"

I think the problem is that Ganesha opens a socket for each protocol (NFS, MOUNT, NLM, etc.). Only one socket can bind to a particular port. We COULD detect the...

Q: why "add_clid" in the "struct nfs4_recovery_backend" returns void instead of a return value?

We probably should check for failure... It wouldn't be too hard to do that.

Q: why "add_clid" in the "struct nfs4_recovery_backend" returns void instead of a return value?

No fsynced data would be lost exactly since that isn't dependent on state recovery. What could be lost is byte range locks, so if a client was in the middle...