[Gluster-users] Not able to list quota

2014-03-26 Thread jonas

Hello,

Im not able to list quotas anymore.

# gluster volume quota Hyxi0xegevajekenohatatewenuhaxa list
operation failed
Quota command failed


From the log:


[2014-03-26 15:50:24.100972] W [socket.c:1494:__socket_proto_state_machine] 
0-socket.management: reading from socket failed. Error (Transport endpoint is 
not connected), peer (127.0.0.1:1021)

Any ideas?
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


[Gluster-users] Catn create volume

2013-12-02 Thread jonas
I upgraded from 3.3.x to 3.4.1 and after that I can create volumes. My 
existing volumes working fine.


# gluster volume create test03 replica 2 transport tcp GlusterFS03:/home/test03 
GlusterFS02:/home/test03
volume create: test03: failed

Any ideas where to check?
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


Re: [Gluster-users] Catn create volume

2013-12-02 Thread jonas


On Mon, 2 Dec 2013, Vijay Bellur wrote:


On 12/02/2013 06:50 PM, jo...@bjorklund.cn wrote:

I upgraded from 3.3.x to 3.4.1 and after that I can create volumes. My
existing volumes working fine.

# gluster volume create test03 replica 2 transport tcp
GlusterFS03:/home/test03 GlusterFS02:/home/test03
volume create: test03: failed

Any ideas where to check?


The glusterd log file in /var/log/glusterfs would be a good place to start.


Is it /var/log/glusterfs/glustershd.log ?
I dont get any information in any of the log files when I try to create a 
volume.

/Jonas
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


Re: [Gluster-users] NFS problem

2010-02-08 Thread Jonas Bulthuis
Hi Shehjar,

That's good to know. I'll try the unfsd.

Thanks for your help.

Kind regards / Met vriendelijke groet,
Jonas Bulthuis


Shehjar Tikoo wrote:
 Jonas Bulthuis wrote:
 Hi Shehjar,

 Thanks for your reply. We may be interested in testing a alpha version
 in the future. I cannot tell for sure right now, but if you can send me
 an e-mail at the time this version becomes available, we can see if we
 can fit it in.

 We're currently running the Gluster FS on Ubuntu (LTS) servers. I can
 access the volumes though the Gluster client on the same machines. Do
 you know whether it's possible to export the Gluster client mount point
 through nfs-kernel-server instead of the user space NFS server? or would
 that be unwise?

 
 It is possible but it is not real solution. Due to the way knfsd
 talks to FUSE, some amount of state in the kernel needs to be kept
 around indefinitely, which causes problems of excessive memory usage.
 unfsd does not cause such a problem.
 
 
 -Shehjar
 
 
 Kind regards / Met vriendelijke groet,
 Jonas Bulthuis


 Shehjar Tikoo wrote:
 Hi

 Due to time constraints, booster has gone untested for the last couple
 of months. I suggest using unfsd over fuse for the time
 being. We'll be releasing an alpha of the NFS translator
 somewhere in March. Let me know if you'd be interested in doing
 early testing?

 Thanks
 -Shehjar

 Jonas Bulthuis wrote:
 Hello,

 I'm using Gluster with cluster/replicate on two servers. On each of
 these servers I'm exporting the replicated volume through the UNFSv3
 booster provided by Gluster.

 Multiple nfs clients are using these storage servers and most of the
 time it seems to work fine. However, sometimes the clients give error
 messages about a 'Stale NFS Handle' when trying to get a directory
 listing of some directory on the volume (not all directories gave this
 problem). Yesterday it happened after reinstalling the client machines.

 All the client machines had the same problem. Rebooting the client
 machines did not help. Eventually, restarting the UNFSv3 server solved
 the problem.

 At least the problem disappeared for now, but, as it happened twice
 in a
 short time now, it seems likely that it will occur again.

 Does anyone have any suggestion on how to permanently solve this
 problem?


 This is the nfs booster configuration we're currently using:

 /etc/glusterfs/cache_acceptation-tcp.vol /nfsexport_acceptation
 glusterfs
 subvolume=cache_acceptation,logfile=/usr/local/var/log/glusterfs/booster_acceptation.log,loglevel=DEBUG,attr_timeout=0




 Any help will be very much appreciated. Thanks in advance.


 
___
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users


Re: [Gluster-users] NFS problem

2010-02-05 Thread Jonas Bulthuis
Hi Shehjar,

Thanks for your reply. We may be interested in testing a alpha version
in the future. I cannot tell for sure right now, but if you can send me
an e-mail at the time this version becomes available, we can see if we
can fit it in.

We're currently running the Gluster FS on Ubuntu (LTS) servers. I can
access the volumes though the Gluster client on the same machines. Do
you know whether it's possible to export the Gluster client mount point
through nfs-kernel-server instead of the user space NFS server? or would
that be unwise?

Kind regards / Met vriendelijke groet,
Jonas Bulthuis


Shehjar Tikoo wrote:
 Hi
 
 Due to time constraints, booster has gone untested for the last couple
 of months. I suggest using unfsd over fuse for the time
 being. We'll be releasing an alpha of the NFS translator
 somewhere in March. Let me know if you'd be interested in doing
 early testing?
 
 Thanks
 -Shehjar
 
 Jonas Bulthuis wrote:
 Hello,

 I'm using Gluster with cluster/replicate on two servers. On each of
 these servers I'm exporting the replicated volume through the UNFSv3
 booster provided by Gluster.

 Multiple nfs clients are using these storage servers and most of the
 time it seems to work fine. However, sometimes the clients give error
 messages about a 'Stale NFS Handle' when trying to get a directory
 listing of some directory on the volume (not all directories gave this
 problem). Yesterday it happened after reinstalling the client machines.

 All the client machines had the same problem. Rebooting the client
 machines did not help. Eventually, restarting the UNFSv3 server solved
 the problem.

 At least the problem disappeared for now, but, as it happened twice in a
 short time now, it seems likely that it will occur again.

 Does anyone have any suggestion on how to permanently solve this problem?


 This is the nfs booster configuration we're currently using:

 /etc/glusterfs/cache_acceptation-tcp.vol /nfsexport_acceptation
 glusterfs
 subvolume=cache_acceptation,logfile=/usr/local/var/log/glusterfs/booster_acceptation.log,loglevel=DEBUG,attr_timeout=0



 Any help will be very much appreciated. Thanks in advance.


 
___
Gluster-users mailing list
Gluster-users@gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users