Hi Shehjar:
On Tue, Nov 2, 2010 at 9:40 PM, Shehjar Tikoo shehj...@gluster.com wrote:
Please file a bug. I'll need the logs in TRACE level for the nfs server
daemon while you run ls on the mount point, also the volume files.
Filed:
Hi Shehjar:
On Fri, Oct 29, 2010 at 12:07 PM, Bernard Li bern...@vanhpc.org wrote:
Thanks, that worked. I copied /etc/glusterd/nfs/nfs-server.vol to the
other server, started glusterfsd and I could mount the volume via NFS
on a client.
I guess I spoke too soon. While I could successfully
On Tue, Nov 2, 2010 at 2:01 PM, Bernard Li bern...@vanhpc.org wrote:
For instance for each brick I have:
/export/share/test/a/b/foo
The resulting NFS mountpoint only shows ./test/a but stops there (a
is empty directory).
Quick update -- now I can see the directory b, but again it's empty
Hi Shehjar:
On Thu, Oct 28, 2010 at 12:34 AM, Shehjar Tikoo shehj...@gluster.com wrote:
Thats not recommended but I can see why this is needed. The simplest way to
run the nfs server for the two replicas is to simply copy over the nfs
volume file from the current nfs server. It will work
Bernard Li wrote:
Hi Shehjar:
The hosts with exports in the replication pool are already running NFS
servers so I need to setup GlusterFS native NFS server on another
server. I am using the following /etc/glusterfs/glusterfsd.vol:
Thats not recommended but I can see why this is needed. The
Hi Shehjar:
The hosts with exports in the replication pool are already running NFS
servers so I need to setup GlusterFS native NFS server on another
server. I am using the following /etc/glusterfs/glusterfsd.vol:
volume gluster01
type protocol/client
option transport-type tcp
option
Hi all:
I'm trying to setup an NFS export using GlusterFS 3.1. I have setup a
replicated volume using the gluster CLI as follows:
Volume Name: share
Type: Replicate
Status: Started
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: gluster01:/export/share
Brick2: gluster02:/export/share
@gluster.org
Sent: Tuesday, October 26, 2010 5:03:02 PM
Subject: [Gluster-users] NFS export issue with GlusterFS 3.1
Hi all:
I'm trying to setup an NFS export using GlusterFS 3.1. I have setup a
replicated volume using the gluster CLI as follows:
Volume Name: share
Type: Replicate
Status: Started
Hi Craig:
On Tue, Oct 26, 2010 at 8:22 PM, Craig Carl cr...@gluster.com wrote:
You should be using the GA release of Gluster 3.1, it includes our NFS
translator.
Yes, I'm using 3.1 GA already.
The download is here -
http://download.gluster.com/pub/gluster/glusterfs/3.1/LATEST/
Bernard Li wrote:
Hi all:
I'm trying to setup an NFS export using GlusterFS 3.1. I have setup a
replicated volume using the gluster CLI as follows:
Volume Name: share
Type: Replicate
Status: Started
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: gluster01:/export/share
Brick2:
On Tue, Oct 26, 2010 at 9:15 PM, Shehjar Tikoo shehj...@gluster.com wrote:
Regarding this pdf, only the portions which show mount commands and the FAQ
section is applicable to 3.1. In 3.1, NFS gets started by default for a
volume started with the volume start command.
So basically you're
11 matches
Mail list logo