[Nfs-ganesha-devel] DISCUSSION: V2.3 workflow and how we proceed

2015-04-24 Thread Frank Filz
So I tried to merge using gerrithub today. The procedure I had intended to follow will not be sustainable as just an extension of the workflow we have used in the past. As a result of this, I did some merges with gerrithub, and then have force-updated the branch to revert it to V2.3-dev-0 (Sorry B

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Timofey Titovets
Malahal, https://github.com/nfs-ganesha/nfs-ganesha/blob/master/src/config_samples/ceph.conf So i can ignore config examples? LOG { Facility { name = FILE; destination = /var/log/nfs-ganesha.log; max_level = FULL_DEBUG;

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Malahal Naineni
EXPORT block doesn't have NFS_Protocols parameter. It can be specified in core params which is an alias to Protocols. Change NFS_Protocols to Protocols. That should avoid some other errors too. You may get into other issues with CEPH fsal specific issues later or it may just work. Regards, Malaha

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Timofey Titovets
I've add it, that i've get from ganesha it wan't create log file, it just copy paste from journalctl LOG { Facility { name = FILE; destination = /var/log/nfs-ganesha.log; max_level = FULL_DEBUG; headers = all;

Re: [Nfs-ganesha-devel] PLEASE READ - Merge nightmare - may not be a dev-1 this week

2015-04-24 Thread Matt W. Benjamin
It seems to me that openafs gerrit (dating back to 2008 or earlier) had an ability to keep sets of patches pushed together, as a kind of changeset. I'll ask around. Matt - "Frank Filz" wrote: > Ok, using gerrithub is really feeling like it's not going to work for > me... > > Merging a pa

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Frank Filz
Using a Path of "/" shouldn't be the problem. Also, that doesn't explain why the FSAL_VFS export isn't working either. Frank > -Original Message- > From: Soumya Koduri [mailto:skod...@redhat.com] > Sent: Friday, April 24, 2015 11:18 AM > To: Timofey Titovets; philippe.den...@cea.fr > Cc:

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Soumya Koduri
>>> # mount -o nfsvers=3 172.20.252.12:/ /mnt -v Looks like you are trying to mount "/" via v3. "/" is reserved for psuedo file system which can be mounted only via "v4" AFAIK. Please try using a different path other than '/' in your Export Block. >>> EXPORT >>> { >>> # Export Id

[Nfs-ganesha-devel] PLEASE READ - Merge nightmare - may not be a dev-1 this week

2015-04-24 Thread Frank Filz
Ok, using gerrithub is really feeling like it's not going to work for me... Merging a patch set with multiple patches is impossible to manage. There's no assistance in keeping track of the order of merging patches. At this moment, my gerrithub next branch is partially merged. This MUST NOT BE REL

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Frank Filz
> I try to explain - what i've successful mount server with nfsv4 and work with > it, but can't do it with nfsv3, and does not matter what FASL i've using (VFS or > Ceph) i.e. i don't have problem with NFSv4 and ai can work with ceph by it, so > beautiful, but if i try to connect with nfsv3, i've g

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Timofey Titovets
I try to explain - what i've successful mount server with nfsv4 and work with it, but can't do it with nfsv3, and does not matter what FASL i've using (VFS or Ceph) i.e. i don't have problem with NFSv4 and ai can work with ceph by it, so beautiful, but if i try to connect with nfsv3, i've get some

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Matt W. Benjamin
Hi, The Ceph FSAL uses the libcephfs (and librados) to consume the cluster. It's not re-exporting a mounted Ceph filesystem. Matt - "Timofey Titovets" wrote: > showmount -e 172.20.252.12 > Export list for 172.20.252.12: > / (everyone) > > 2015-04-24 10:33 GMT+03:00 DENIEL Philippe : > > H

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Malahal Naineni
Timofey Titovets [nefelim...@gmail.com] wrote: > showmount -e 172.20.252.12 > Export list for 172.20.252.12: > / (everyone) Looks like you have not exported anything, at least that is what the above line says. "/" is pseudo root. What version are you using? I would suggest you use the latest V2.2.

Re: [Nfs-ganesha-devel] rebase oddity

2015-04-24 Thread Frank Filz
> On 4/24/15 3:08 AM, Dominique Martinet wrote: > > Yeah, this was meant to be in the V2.2.0 tag but introduced some bug > > and pruned out. > > > This is not mentioned anywhere in this list. This list is our communications > log, not some chat somewhere. > > > > I guess the proper way forward t

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread Timofey Titovets
showmount -e 172.20.252.12 Export list for 172.20.252.12: / (everyone) 2015-04-24 10:33 GMT+03:00 DENIEL Philippe : > Hi, > > what does " showmount -e 172.20.252.12 " say ? This way, you'll see if > Ganesha was capable of building the export entries. > My knowledge of CEPH is weak, so I forward yo

Re: [Nfs-ganesha-devel] rebase oddity

2015-04-24 Thread Malahal Naineni
William Allen Simpson [william.allen.simp...@gmail.com] wrote: > On 4/24/15 3:08 AM, Dominique Martinet wrote: > > Yeah, this was meant to be in the V2.2.0 tag but introduced some bug and > > pruned out. > > > This is not mentioned anywhere in this list. This list is our > communications log, not

Re: [Nfs-ganesha-devel] rebase oddity

2015-04-24 Thread William Allen Simpson
On 4/24/15 3:08 AM, Dominique Martinet wrote: > Yeah, this was meant to be in the V2.2.0 tag but introduced some bug and > pruned out. > This is not mentioned anywhere in this list. This list is our communications log, not some chat somewhere. > I guess the proper way forward that doesn't break

Re: [Nfs-ganesha-devel] [Nfs-ganesha-support] Troubles with configuration

2015-04-24 Thread DENIEL Philippe
Hi, what does " showmount -e 172.20.252.12 " say ? This way, you'll see if Ganesha was capable of building the export entries. My knowledge of CEPH is weak, so I forward your question to nfs-gamesha-devel. In particular, I do not know if: - CEPH support open_by_handle_at() syscall - FS

Re: [Nfs-ganesha-devel] rebase oddity

2015-04-24 Thread Dominique Martinet
William Allen Simpson wrote on Thu, Apr 23, 2015 at 10:34:36PM -0400: > On 4/23/15 9:56 PM, William Allen Simpson wrote: > > To be clear, Fix FATTR4_SUPPORTED_ATTRS isn't my patch, and > > was sucked up somehow from the -rc past, probably -rc8. > > > > Where is this supposed to be? > > Verified thi

[Nfs-ganesha-devel] Fwd: [nfs-ganesha.github.com] Update news to release V2.2 (#1)

2015-04-24 Thread DENIEL Philippe
Hi List, have you seen that pull request (made apparently online from github.com) Regards Philippe Forwarded Message Subject:[nfs-ganesha.github.com] Update news to release V2.2 (#1) Date: Thu, 23 Apr 2015 14:48:06 -0700 From: Timofey Reply-To: nfs-