On 03/14/2013 10:57 AM, Emmanuel Dreyfus wrote:
With 3.4.0alpha2, ca processremains stuck on a FUSE operation on the
client. glusterfs client log says:
[2013-03-14 00:40:42.269307] W
[client-rpc-fops.c:1588:client3_3_finodelk_cbk]
0-gfs33-client-3: remote operation failed: Invalid
On 14.03.2013 09:29, Varun Shastry wrote:
Hi Nux,
This problem will be fixed once http://review.gluster.org/4495 goes
into 3.4 (already merged on master).
Thanks
Varun Shastry
Lovely, so now it's just a case of waiting for Kaleb to package it. :)
BTW any ETA for alpha3 or whatever is the
On 14.03.2013 03:26, krish wrote:
A client attempts to bind to a port before connecting to the server.
On Linux systems, we check if the port is reserved by looking for it
in /proc/sys/net/ipv4/ip_local_reserved_ports. If
/proc/sys/net/ipv4/ip_local_reserved_port contained only a newline
(viz.
Hi,
This morning one of the gluster 3.4 servers went crazy, to be honest
with you no idea what I did that caused it, but it's only on this one
machine.
Glusterd and Glusterfsd refuse to start and this shows up in the logs.
Rdma.so is indeed missing, but I am not using rdma ... and it is
It's here:
https://bugzilla.redhat.com/show_bug.cgi?id=918917
Mostly it includes the stuff that got bumped from Alpha 2, plus the
Fedora specfile resync, plus some other stuff (e.g. the volume sync
fix) that had come up in hallway conversations last week. If you can
think of any other
On Wed, 13 Mar 2013 16:04:14 -0700
Anand Avati anand.av...@gmail.com wrote:
On Wed, Mar 13, 2013 at 3:05 PM, Edward Shishkin edw...@redhat.com
wrote:
Dear all,
This requires openssl of version = 1.0.1c
Is it possible to upgrade the openssl on the machines, which
perform smoke
hi, Tobias
Maybe the answer is TRUE, because WORM xlator is based on Read-only xlator.
According to the source code, the only difference between WORM and
Read-only is : on the volume with WORM xlator, file could be opened with mode
O_APPEND, that means you could append data to the
