Not adding an extra column is least likely to break any scripts that
currently parse the status output by splitting on spaces.
On Wed, 2014-11-26 at 20:27 +0530, Atin Mukherjee wrote:
I would vote for 2nd one.
~Atin
On 11/26/2014 06:49 PM, Mohammed Rafi K C wrote:
Hi All,
We
connected clients cannot support the feature being set. These clients
need to be upgraded or disconnected before running this command again
On Thu, 2014-05-29 at 10:34 +0800, Franco Broi wrote:
OK. I've just unmounted the data2 volume from a machine called tape1,
and now try to remount - it's hanging
Hi
My clients are running 3.4.1, when I try to mount from lots of machine
simultaneously, some of the mounts hang. Stopping and starting the
volume clears the hung mounts.
Errors in the client logs
[2014-05-28 01:47:15.930866] E
[client-handshake.c:1741:client_query_portmap_cbk]
OK. I've just unmounted the data2 volume from a machine called tape1,
and now try to remount - it's hanging.
/bin/sh /sbin/mount.glusterfs nas5-10g:/data2 /data2 -o
rw,log-level=info,log-file=/var/log/glusterfs/glusterfs_data2.log
on the server
# gluster vol status
Status of volume: data2
