On 04/28/15 18:13, Frank Filz wrote:
(...)
The problem with a longer that one week cycle is that we get larger and
larger volumes of patches. With the right tools, we can sustain a weekly
cycle.
We introduced the 1-week cycle to regulate/sort patches, for we had no
other way of doing it when
Hi Frank,
3 commits for this week:
# git log --oneline V2.3-dev-8..HEAD
01812a3 TRAVIS/CI: remove ceph from build made by Travis/CI
fb4a5a7 Do not register NFS port is configuration file do not ask
for NFS support
2a43107 NFSv4.1/pNFS/Flexible Files: add Flexible Files Layout XDR
Hi,
in order to add more tests to my non-regression test suite, I'd like to
worry about NFSv4 acl.
Currently, a POSIX FS manages ACLs via a special xattr named
system.posix_acl_access (and uses getxattr()/setxattr() to deal with
them). The xattr can be accessed either by
The NFSv4 ACLs are no
On 09/28/17 02:18, Dominique Martinet wrote:
Frank Filz wrote on Wed, Sep 27, 2017 at 10:50:00AM -0700:
One source of “fd leaks” is that the global fd, which is used for
getattrs, is no longer well managed. I have some ideas in progress on
how to better manage this, but discussion has stalled
nk you for that.
What do you mean by no compliancy to support_ex, does that imply a
specific range of ganesha versions? other constraints?
Regards,
Aurélien
2018-01-04 13:18 GMT+01:00 DENIEL Philippe <philippe.den...@cea.fr
<mailto:philippe.den...@cea.fr>>:
Hi Aur
Hi Aurélien,
I can provide you an alternate solution, still nfs-ganesha based. For
the need of a project, I developed an open-source library that emulate a
POSIX namespace using a KVS (for metadata) and an object store (for
data). For example, you can use REDIS and RADOS. I have written a
Hi,
from a "stratospheric" point of view, I see a potentially big issue
ahead for such a feature : FSAL has been designed to be quite close to
POSIX behavior, CIFS follows the Microsoft File System semantics, which
is pretty different from POSIX.
My experience with 9p integration in Ganesha
