[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pull up NTIRPC #72

2017-09-13 Thread GerritHub 
>From :

william.allen.simp...@gmail.com has uploaded this change for review. ( 
https://review.gerrithub.io/378363


Change subject: Pull up NTIRPC #72
..

Pull up NTIRPC #72

 * (svc_rqst) faster shutdown

Change-Id: I68c85b55cced4c0bbf2b70ada24980faa4361139
Signed-off-by: William Allen Simpson 
---
M src/libntirpc
1 file changed, 1 insertion(+), 1 deletion(-)



  git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha 
refs/changes/63/378363/1
-- 
To view, visit https://review.gerrithub.io/378363
To unsubscribe, visit https://review.gerrithub.io/settings

Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-MessageType: newchange
Gerrit-Change-Id: I68c85b55cced4c0bbf2b70ada24980faa4361139
Gerrit-Change-Number: 378363
Gerrit-PatchSet: 1
Gerrit-Owner: william.allen.simp...@gmail.com
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] yesterdays conf.-call

2017-09-13 Thread Daniel Gryniewicz 

On 09/13/2017 09:41 AM, William Allen Simpson wrote:

On 9/13/17 9:02 AM, Daniel Gryniewicz wrote:
True.  I'd forgotten I had to raise FD limits in my environment (to 
99) to allow valgrind to pass. 


Probably excessive as there are only 65K ports in both TCP and UDP.



True, but valgrind uses a ton of FDs for it's own use, so I just maxed 
it out.


Daniel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Continuing CI pain

2017-09-13 Thread Niels de Vos 
On Wed, Sep 13, 2017 at 09:38:21AM -0400, William Allen Simpson wrote:
> On 9/13/17 9:19 AM, Niels de Vos wrote:
> > On Wed, Sep 13, 2017 at 08:07:24AM -0400, William Allen Simpson wrote:
> > > On 9/13/17 4:39 AM, Niels de Vos wrote:
> > > > Why creating the logfile fail is not clear to me. Maybe something in the
> > > > packaging was changed and the /var/log/ganesha/ directory is not
> > > > writable for the ganesha.nfsd process anymore? Have changes for running
> > > > as non-root been merged, maybe?
> > > > 
> > > Why does the gluster test suite work, but not the cthon?  What are the
> > > setup differences?
> > 
> > I am not sure which test you are refering to, do you have a link?
> > 
> attached.
> 
> 
> > It may be a build-only test that succeeds.
> 
> Is that +1 a build-only test?

Yes, that is the case. RPMs are built, but this test does not install,
configure or run NFS-Ganesha.

> > At least PyNFS tests fail in
> > a similar way:
> >https://ci.centos.org/view/NFS-Ganesha/job/nfs_ganesha_pynfs/1039/console
> > 
> Sounds like that could be a 3rd test suite.

There are several tests configured, not all are active, and not all run
when a patch is uploaded to Gerrit. All jobs are listed here:
  https://ci.centos.org/view/NFS-Ganesha/

Niels

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] yesterdays conf.-call

2017-09-13 Thread William Allen Simpson 

On 9/13/17 9:02 AM, Daniel Gryniewicz wrote:
True.  I'd forgotten I had to raise FD limits in my environment (to 99) to allow valgrind to pass.  


Probably excessive as there are only 65K ports in both TCP and UDP.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Continuing CI pain

2017-09-13 Thread William Allen Simpson 

On 9/13/17 9:19 AM, Niels de Vos wrote:

On Wed, Sep 13, 2017 at 08:07:24AM -0400, William Allen Simpson wrote:

On 9/13/17 4:39 AM, Niels de Vos wrote:

Why creating the logfile fail is not clear to me. Maybe something in the
packaging was changed and the /var/log/ganesha/ directory is not
writable for the ganesha.nfsd process anymore? Have changes for running
as non-root been merged, maybe?


Why does the gluster test suite work, but not the cthon?  What are the
setup differences?


I am not sure which test you are refering to, do you have a link?


attached.


It may be a build-only test that succeeds. 


Is that +1 a build-only test?


At least PyNFS tests fail in
a similar way:
   https://ci.centos.org/view/NFS-Ganesha/job/nfs_ganesha_pynfs/1039/console


Sounds like that could be a 3rd test suite.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Continuing CI pain

2017-09-13 Thread Niels de Vos 
On Wed, Sep 13, 2017 at 08:07:24AM -0400, William Allen Simpson wrote:
> On 9/13/17 4:39 AM, Niels de Vos wrote:
> > Why creating the logfile fail is not clear to me. Maybe something in the
> > packaging was changed and the /var/log/ganesha/ directory is not
> > writable for the ganesha.nfsd process anymore? Have changes for running
> > as non-root been merged, maybe?
> > 
> Why does the gluster test suite work, but not the cthon?  What are the
> setup differences?

I am not sure which test you are refering to, do you have a link?

It may be a build-only test that succeeds. At least PyNFS tests fail in
a similar way:
  https://ci.centos.org/view/NFS-Ganesha/job/nfs_ganesha_pynfs/1039/console

Niels

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

[Nfs-ganesha-devel] I RE: Setup/Configuration problem for a proxy with nfs-ganesha V2.6-dev.7

2017-09-13 Thread Stephan Walter 
Hi all,

I have now tried to use the ganesha server instead of the nfs-kernel-server as 
initial exporter, but run into even more problems.

I stopped the nfs-kernel-server and then started the ganesha server with the 
following commandline and config file

sudo ganesha.nfsd -f 
nfs-ganesha-build/test/ganesha.min_test.conf -L ./ganesha-export.logfile -N 
NIV_DEBUG -F

The ganehsa.min_test.conf is:
EXPORT
{
Export_Id = 2;
Path = /home/swalter/nfs-org;
Pseudo = /home/swalter/nfs-org;
Access_Type = RW;
#Squash = None;
FSAL
{
Name = VFS;
   }
}
So this is equal to the basic config file.

I think the Ganesha server works fine, since I get the following output:
Sudo showmount -e localhost
Export list for localhost:
/home/swalter/nfs-org (everyone)

Afterwards, I started the Ganesha-Proxy with the same config file as before - 
just another ip, since I have cloned the VM.

While the proxy start successfully when I use the nfs-kernel-server, it hangs 
with the ganesha server as source for the proxy.

I have seen, that there seems to be a problem with the xid, if I interpret the 
logfile in the right way. I attached the logfile of the proxy to this mail.


UPDATE:
nfs-kernel-server -> Ganesha-Proxy -> NFS-Client

I played also a bit around with the above configuration to debug, what lead to 
the corruption of the directory.

It seems, that I can remove files , copy and cat files as much as I want. Also 
I can use md5sum or so to access the data within the files. But when I try to 
use 'VIM' to save an existing file, or open a new one, I get the following 
error:
"foobar"
"foobar" E212: Can't open file for writing
Press ENTER or type command to continue

Now I get the following output for the ll commands on the client

ll
ls: reading directory '.': Permission denied
total 0

sudo ls -hal
ls: cannot open directory '.': Permission denied

cd ..  && ll
total 1040
drwx--x--x  3 swalter swalter4096 Sep 13 14:51 ./
drwxr-xr-x 23 swalter swalter4096 Sep 13 14:39 ../
-rw-r--r--  1 swalter swalter 1048576 Sep 13 14:15 1M.data
drw---  2 swalter swalter4096 Sep 13 14:52 barfoo/
-rw-r--r--  1 swalter swalter  42 Sep 13 14:15 md5sum.check

It has shown, that the barfoo directory has lost the X value, so that I no 
longer can access it. If I add it again with chmod 711 I can again access the 
directory and files

Cd barfoo && ll
total 12
drwx--x--x 2 swalter swalter 4096 Sep 13 14:52 ./
drwx--x--x 3 swalter swalter 4096 Sep 13 14:51 ../
-rw-r--r-- 1 swalter swalter7 Sep 13 14:27 barfoo
-- 1 swalter swalter0 Mai  3  1971 .foobar.swp

As we can see is there a swp file from vim without permissions.   I can now 
also access all the data and delete the directory again.

So it is not clear to me, why this happens.

Another interesting point is maybe the following

mkdir test
ll
drwxr-xr-x  2 swalter swalter  4096 Sep 13 14:39 test/

sudo mount -t nfs4 192.168.56.101:/nfs-ganesha-proxy ./test -v
ll
drwx--x--x  3 swalter swalter  4096 Sep 13 14:26 test/

So the permissions of the directory has changed. I don't know, if this is 
correct or not. But I don't think, that this is important, since the same error 
occurs, when I chance the permissions to 755 at the nfs-kernel-server, what 
also change all the permissions at the nfs-client.

Best regards,

Stephan


From: Stephan Walter [mailto:stephan.wal...@emea.nec.com]
Sent: 13 September 2017 11:31
To: patrice.lu...@cea.fr; nfs-ganesha-devel@lists.sourceforge.net
Subject: [** SUSPICIOUS EMAIL **] Re: [Nfs-ganesha-devel] Setup/Configuration 
problem for a proxy with nfs-ganesha V2.6-dev.7

Hi Patrice,

Thank you very much for your help. I was now able to start the ganesha-proxy 
and also mount it on the test vm. Unfortunately, the proxy seems to corrupt the 
data.

I will now explain the configuration in detail for a better understanding.

I use in total 3 VMs


1.   GANESHA-PROXY192.168.56.101

2.   NFS-CLIENT192.168.56.102

3.   NFS-ORG 192.168.56.103


Now to the settings on the specific VM

NFS-ORG
The first problem I faced after I used your setup was, that I exported 
directories that belongs to root, what lead to a conflict with the root_squash 
option of the original nfs export. Therefore, I modified the setting


/etc/exports:
/home/swalter/nfs-org *(rw,sync)

ll /home/swalter/nfs-org
drwxr-xr-x  2 swalter swalter 4096 Sep 13 10:33 ./
drwxr-xr-x 21 swalter swalter 4096 Sep 13 10:33 ../
-rw-r--r--  1 swalter swalter 1034 Sep 13 10:33 foobar.txt

After that, I restarted the nfs service to export the new directory
sudo service nfs-kernel-server restart

GANESHA-PROXY
cat nfs-ganesha-build/test/ganesha.proxy_min.conf
EXPORT
{
# Export Id (mandatory, each EXPORT must have a unique Export_

Re: [Nfs-ganesha-devel] yesterdays conf.-call

2017-09-13 Thread Daniel Gryniewicz 
True.  I'd forgotten I had to raise FD limits in my environment (to 
99) to allow valgrind to pass.  The other thing I do is set 
--max-stackframe=3280592 on the valgrind command line, but with those 
two changes, pyNFS "all" passes for me under valgrind.


Daniel

On 09/13/2017 08:53 AM, Swen Schillig wrote:

In yesterdays conf.-call we spoke about pynfs-errors while running
valgrind.

I spent some time today to find out the reason and I'm afraid that was
a user error (so me).

A good few pynfs-tests go to numeric limits for a standard process
and if ganesha is executed under valgrind those limits are hit.
In my case it was the soft-limit for number of open files.
Once increased, pynfs succeeds.
At least the tests based on file creations.

There are other tests which might fail if executed as part of
the "all" test-suite but do succeed if executed in a smaller set.
E.g. MKLINK RDDR1 RDDR2 RDDR3 RDDR4 RDDR8 RDDR11 RDDR12 RENEW3 RLOWN1
RD10 RD11

Anyhow, just FYI.

Cheers Swen


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

[Nfs-ganesha-devel] yesterdays conf.-call

2017-09-13 Thread Swen Schillig 
In yesterdays conf.-call we spoke about pynfs-errors while running
valgrind.

I spent some time today to find out the reason and I'm afraid that was
a user error (so me).

A good few pynfs-tests go to numeric limits for a standard process
and if ganesha is executed under valgrind those limits are hit.
In my case it was the soft-limit for number of open files.
Once increased, pynfs succeeds.
At least the tests based on file creations.

There are other tests which might fail if executed as part of 
the "all" test-suite but do succeed if executed in a smaller set.
E.g. MKLINK RDDR1 RDDR2 RDDR3 RDDR4 RDDR8 RDDR11 RDDR12 RENEW3 RLOWN1
RD10 RD11

Anyhow, just FYI.

Cheers Swen


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Continuing CI pain

2017-09-13 Thread William Allen Simpson 

On 9/13/17 4:39 AM, Niels de Vos wrote:

Why creating the logfile fail is not clear to me. Maybe something in the
packaging was changed and the /var/log/ganesha/ directory is not
writable for the ganesha.nfsd process anymore? Have changes for running
as non-root been merged, maybe?


Why does the gluster test suite work, but not the cthon?  What are the
setup differences?

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: TIRPC_DEBUG_FLAG_DEFAULT

2017-09-13 Thread William Allen Simpson 

On 9/13/17 12:10 AM, William Allen Simpson wrote:

On 9/12/17 1:25 PM, William Allen Simpson wrote:

On 9/12/17 10:12 AM, GerritHub wrote:

william.allen.simp...@gmail.com has uploaded this change for *review*.

View Change 


NTIRPC should configure exactly like Ganesha.  It's less confusing.


On the ticket, Frank made a number of suggestions.  I've done most of
them.  There are now explicitly equivalent parallel debug_flags
combinations for errors, warnings, events, and debug.

Moving the RPC_Debug_Flags parameter itself into the LOG block causes a
stack error, so I probably did it wrong.  Took that out again.


In patch set 6, after a bit of sleep, managed to get that working.

In patch set 7, updated documentation to match.

Would appreciate Malahal and Swen taking a look -- Swen reported that
Malahal's patch of a year ago wasn't setting flags when Swen tried
ALL=FULL_DEBUG.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Known limitations of FSAL Ceph

2017-09-13 Thread Supriti Singh 
Thank you for opening ticket on ceph tracker. For now, is someone already aware 
of known limitations for FSAL Ceph.



Thanks,
Supriti 


--
Supriti Singh SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham 
Norton,
HRB 21284 (AG Nürnberg)
 



>>> Ramana Raja  08/29/17 5:41 PM >>>
Thanks for raising this. I've created a Ceph tracker ticket for now,
http://tracker.ceph.com/issues/21172

Documentation on NFS-Ganesha/CephFS integration is missing.

-Ramana

On Tue, Aug 29, 2017 at 6:04 PM, Daniel Gryniewicz  wrote:
> 
> Not that I'm aware of.  Matt (on the RGW team) wrote that, and as far as
> I know, no one from the CephFS team has written a similar document.
> 
> Daniel
> 
> On 08/29/2017 02:27 AM, Supriti Singh wrote:
> > Hello,
> > 
> > For FSAL RGW,
> > https://github.com/ceph/ceph/blob/master/doc/radosgw/nfs.rst#supported-operations
> > this list down the operations that are not supported with FSAL RGW
> > currently.
> > 
> > Is there a similar list for FSAL Ceph as well?
> > 
> > Thanks,
> > Supriti
> > 
> > --
> > Supriti Singh
> > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
> > HRB 21284 (AG Nürnberg)
> > 
> > 
> > 
> > --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > 
> > 
> > 
> > ___
> > Nfs-ganesha-devel mailing list
> > Nfs-ganesha-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
> > 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
> 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Setup/Configuration problem for a proxy with nfs-ganesha V2.6-dev.7

2017-09-13 Thread Stephan Walter 
Hi Patrice,

Thank you very much for your help. I was now able to start the ganesha-proxy 
and also mount it on the test vm. Unfortunately, the proxy seems to corrupt the 
data.

I will now explain the configuration in detail for a better understanding.

I use in total 3 VMs


1.   GANESHA-PROXY192.168.56.101

2.   NFS-CLIENT192.168.56.102

3.   NFS-ORG 192.168.56.103


Now to the settings on the specific VM

NFS-ORG
The first problem I faced after I used your setup was, that I exported 
directories that belongs to root, what lead to a conflict with the root_squash 
option of the original nfs export. Therefore, I modified the setting


/etc/exports:
/home/swalter/nfs-org *(rw,sync)

ll /home/swalter/nfs-org
drwxr-xr-x  2 swalter swalter 4096 Sep 13 10:33 ./
drwxr-xr-x 21 swalter swalter 4096 Sep 13 10:33 ../
-rw-r--r--  1 swalter swalter 1034 Sep 13 10:33 foobar.txt

After that, I restarted the nfs service to export the new directory
sudo service nfs-kernel-server restart


GANESHA-PROXY
cat nfs-ganesha-build/test/ganesha.proxy_min.conf
EXPORT
{
# Export Id (mandatory, each EXPORT must have a unique Export_Id)
Export_Id = 77;

# Exported path (mandatory)
#path exported by background nfs server
#Path = /tmp;
#Path = /nfs-org;
Path = /home/swalter/nfs-org;

# Pseudo Path (required for NFS v4)
#path exported by proxy to nfs clients
#Pseudo = /tmp_proxy;
Pseudo = /nfs-ganesha-proxy;

# Required for access (default is None)
# Could use CLIENT blocks instead
Access_Type = RW;

# Exporting FSAL
FSAL {
Name = PROXY;
}
}

PROXY {
Remote_Server {
Srv_Addr = 192.168.56.103;
}
}

After that, I killed the old ganesha server with kill -s SIGTERM  and then 
restarted it again with
sudo ganesha.nfsd -f nfs-ganesha-build/test/ganesha.proxy_min.conf -L 
./ganesha-proxy.logfile -N NIV_DEBUG -F

There is no directory /nfs-ganesha-proxy at this VM, what seems to me right, 
but I am not sure!

NFS-CLIENT

1.   TEST

Mount the nfs from the original NFS server

sudo mount -t nfs4 192.168.56.103:/home/swalter/nfs-org ./nfs-dummy/ -v

I was able to mount the directory, read and modify the foobar.txt and also 
unmount the nfs volume again. So I think everything works fine.

2.   TEST

Mount the nfs from the ganesha-proxy

sudo mount -t nfs4 192.168.56.101:/nfs-ganesha-proxy ./ganesha-dummy/ -v

I was able to mount the directory, read and modify the foobar.txt, but after a 
relatively short time, I get the following output:



ls ganesha-dummy/

ls: reading directory 'ganesha-dummy/': Permission denied

On NFS-ORG I get then the following output

ll nfs-org
ls: cannot access 'nfs-org/1G.data': Permission denied
ls: cannot access 'nfs-org/foobar.txt': Permission denied
total 0
d? ? ? ? ?? ./
d? ? ? ? ?? ../
-? ? ? ? ?? 1G.data
-? ? ? ? ?? foobar.txt

For this particular situation, I tried to copy a 1GB File with random data from 
the NFS-CLIENT to the NFS volume.

I would assume, that there is some kind of data corruption.

I will try today also a Ganesha->Ganesha-Proxy->NFC-Client setup, to be sure, 
that the NFS-Server->Ganesha-PROXY is not the source of the problem.

Best regards,

Stephan

From: LUCAS Patrice [mailto:patrice.lu...@cea.fr]
Sent: 12 September 2017 13:10
To: nfs-ganesha-devel@lists.sourceforge.net
Subject: Re: [Nfs-ganesha-devel] Setup/Configuration problem for a proxy with 
nfs-ganesha V2.6-dev.7

Hello Stephan,


The proxy doc on the github page is maybe a bit outdated.

With latest versions of ganesha, no need to have an additionnal binary. You 
only need to launch the main ganesha.nfsd binary.

Could you explain your simple test configuration so we could try to provide to 
you a correct configuration file ?

Below is an example of a simple updated ganesha conf file to re-export a /tmp 
dir from an nfs server :

===
EXPORT
{
# Export Id (mandatory, each EXPORT must have a unique Export_Id)
Export_Id = 77;

# Exported path (mandatory)
#path exported by background nfs server
Path = /tmp;

# Pseudo Path (required for NFS v4)
#path exported by proxy to nfs clients
Pseudo = /tmp_proxy;

# Required for access (default is None)
# Could use CLIENT blocks instead
Access_Type = RW;

# Exporting FSAL
FSAL {
Name = PROXY;
}
}

PROXY {
Remote_Server {
Srv_Addr = XXX.XXX.XXX.XXX;
}
}
==


Regards,
Patrice LUCAS

On 09/11/17 18:00, Stephan Walter wrote:
Hi,

I run into some problems with the configuration

Re: [Nfs-ganesha-devel] Continuing CI pain

2017-09-13 Thread Niels de Vos 
On Tue, Sep 12, 2017 at 06:41:49PM -0400, William Allen Simpson wrote:
> On 9/12/17 6:06 PM, Frank Filz wrote:
> > So this failure:
> > 
> > https://ci.centos.org//job/nfs_ganesha_cthon04/1436/console
> > 
> > Is an example of where we need some improvement. I looked at the top and
> > scrolled down to the end. I have no idea why it failed. This is a case of
> > too much information without a concise error report.
> > 
> Installed:
>   libntirpc.x86_64 0:1.6.0-dev.7.el7.centos
>   nfs-ganesha.x86_64 0:2.6-dev.7.el7.centos
>   nfs-ganesha-gluster.x86_64 0:2.6-dev.7.el7.centos
> 
> Complete!
> + systemctl start nfs-ganesha
> Job for nfs-ganesha.service failed because the control process exited with
> error code. See "systemctl status nfs-ganesha.service" and "journalctl -xe"
> for details.
> Build step 'Execute shell' marked build as failure
> Finished: FAILURE
> 
> ===
> 
> Why not print "systemctl status nfs-ganesha.service" and "journalctl -xe"?
> 
> Originally I assumed that it was some obscure problem with my code, but
> then I looked around, and it seems to be all the submissions for
> nfs_ganesha_cthon04 at the moment

The additional information will now be logged as well. This change in
the centos-ci branch does it:

  https://github.com/nfs-ganesha/ci-tests/pull/14/files

A (manually started) test run logs the errors more clearly:

  https://ci.centos.org/job/nfs_ganesha_cthon04/1439/console


Sep 13 09:33:41 n9.pufty.ci.centos.org bash[20711]: 13/09/2017 09:33:41 : epoch 
59b8ed65 : n9.pufty.ci.centos.org : ganesha.nfsd-20711[main] 
create_log_facility :LOG :CRIT :Cannot create new log file 
(/var/log/ganesha/ganesha.log), because: Permission denied
Sep 13 09:33:41 n9.pufty.ci.centos.org bash[20711]: 13/09/2017 09:33:41 : epoch 
59b8ed65 : n9.pufty.ci.centos.org : ganesha.nfsd-20711[main] init_logging :LOG 
:FATAL :Create error (Permission denied) for FILE 
(/var/log/ganesha/ganesha.log) logging!
Sep 13 09:33:41 n9.pufty.ci.centos.org systemd[1]: nfs-ganesha.service: control 
process exited, code=exited status=2
Sep 13 09:33:41 n9.pufty.ci.centos.org systemd[1]: Failed to start NFS-Ganesha 
file server.
Sep 13 09:33:41 n9.pufty.ci.centos.org systemd[1]: Unit nfs-ganesha.service 
entered failed state.
Sep 13 09:33:41 n9.pufty.ci.centos.org systemd[1]: nfs-ganesha.service failed.


Why creating the logfile fail is not clear to me. Maybe something in the
packaging was changed and the /var/log/ganesha/ directory is not
writable for the ganesha.nfsd process anymore? Have changes for running
as non-root been merged, maybe?

HTH,
Niels

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Ganesha locking issues.

2017-09-13 Thread domantas.speciunas 

HI,

Anyone had tested Gluster + Ganesha NFS for IBM MQ? In our organization we 
trying to onboard  Gluster + Ganesha NFS  and use it for  IBM MQ and 
encountered some troubles with Ganesha, I yesterday mentioned that on Ganesha 
Dev call.  

IBM has standard test to ensure that NAS is working with their  MQ for which 
they provide amqmfsck utility.  

https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.5.0/com.ibm.mq.pla.doc/q005820_.htm
http://www-01.ibm.com/support/docview.wss?uid=swg21433474

For us, Gluser + fuse  mount is working fine while Gluster with Ganesha NFS 
completely fails IBM MQ  concurrency test. It goal to ensure that 2 instances 
of   amqmfsck (IBM NAS check utility) running on different servers are trying 
to update same file on NAS. It  just use general unlock(fcntl ), lock (fcntl),  
 lseek, and write system calls, only fast enough. I  did not measure update 
speed,  but it is times per second. I am running Gluster 3(2+1)  dual 
replication  + arbiter node. On top of it Ganesha.   (I also tried usual 2 
repli and 3 repli, increase gluster. network.ping-timeout  timeout to 42, 
Lease_Lifetime=60/ Grace_Period=120  in ganesha result the same). 
Also I tried to mount with/without sync,noatime,mand options.
Is it possible to fix this issue? It looks like Ganesha is having issues with 
locking. 
  


 
2
Start a second copy of this program with the same parameters on another server.
Writing to test file. This will normally complete within about 60 seconds.
..
AMQ5667: Error executing system call 'fcntl(F_SETLKW)[c]' on file
'/cftha/testas/amqmfsck.wrt', errno 2 ('No such file or directory').
[mqm@lsp7090d cftha]$


1
Start a second copy of this program with the same parameters on another server.
Writing to test file. This will normally complete within about 60 seconds.
...
The tests on the directory completed successfully.
1. iteration done
2
Start a second copy of this program with the same parameters on another server.
Writing to test file. This will normally complete within about 60 seconds.
...
AMQ5667: Error executing system call 'fcntl(F_SETLKW)[c]' on file
'/cftha/test2/amqmfsck.wrt', errno 2 ('No such file or directory').
[mqm@lsp7090d test2]$



System call: fcntl(fd,F_SETLK,F_UNLCK)
System call: fcntl(fd,F_SETLKW,F_WRLCK)
System call: lseek(fd,0,SEEK_END)
System call: write(fd,data)
System call: fcntl(fd,F_SETLK,F_UNLCK)
System call: fcntl(fd,F_SETLKW,F_WRLCK)
System call: lseek(fd,0,SEEK_END)
System call: write(fd,data)
System call: fcntl(fd,F_SETLK,F_UNLCK)
System call: fcntl(fd,F_SETLKW,F_WRLCK)
AMQ5667: Error executing system call 'fcntl(F_SETLKW)[c]' on file
'/cftha/test3/amqmfsck.wrt', errno 2 ('No such file or directory').
[mqm@lsp7091d ~]$



System call: fcntl(fd,F_SETLK,F_UNLCK)
System call: fcntl(fd,F_SETLKW,F_WRLCK)
System call: lseek(fd,0,SEEK_END)
System call: write(fd,data)
System call: fcntl(fd,F_SETLK,F_UNLCK)
System call: fcntl(fd,F_SETLKW,F_WRLCK)
System call: lseek(fd,0,SEEK_END)
System call: write(fd,data)
System call: fcntl(fd,F_SETLK,F_UNLCK)
System call: fcntl(fd,F_SETLKW,F_WRLCK)
System call: lseek(fd,0,SEEK_END)
System call: write(fd,data)
System call: fcntl(fd,F_SETLK,F_UNLCK)
System call: fcntl(fd,F_SETLKW,F_WRLCK)
AMQ5667: Error executing system call 'fcntl(F_SETLKW)[c]' on file
'/cftha/test3/amqmfsck.wrt', errno 2 ('No such file or directory').
[mqm@lsp7090d ~]$

Mount:
vip1:/cft on /cftha type nfs4 
(rw,relatime,sync,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.36.16.53,local_lock=none,addr=10.36.16.77)
[mqm@lsp7090d ~]$




[root@lsp7152c ~]# cat /etc/ganesha/ganesha.conf
NFSv4
{
# Lifetime for NFSv4 Leases
Lease_Lifetime = 40;
Grace_Period = 80;
}
%include 
"/var/run/gluster/shared_storage/nfs-ganesha/exports/export.testvol.conf"
%include "/var/run/gluster/shared_storage/nfs-ganesha/exports/export.mqm.conf"
%include "/var/run/gluster/shared_storage/nfs-ganesha/exports/export.cft.conf"
[root@lsp7152c ~]#


[root@lsp7152c exports]# cat export.cft.conf
#
EXPORT{
  Export_Id = 4;
  Path = "/cft";
  FSAL {
   name = GLUSTER;
   hostname="localhost";
  volume="cft";

   }
Delegations = none;
  Access_type = RW;
  Disable_ACL = true;
  Squash="No_root_squash";
  Pseudo="/cft";
  Protocols = "3", "4" ;
  Transports = "UDP","TCP";
  SecType = "sys";
}

[root@lsp7152c exports]#


[root@lsp7152c exports]# g v inf cft

Volume Name: cft
Type: Replicate
Volume ID: aac3aba2-66d9-4e64-b5b1-a9dbd96889af
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: lsp7153c:/rhgs/brick2/2
Brick2: lsp7154c:/rhgs/brick2/2
Brick3: lsp7152c:/rhgs/brick_a2/2 (arbiter)
Options Reconfigured:
features.scrub-throttle: lazy
features.scrub-freq: daily
features.scrub: Active
features