On 04/03/2012 03:25 AM, Brian Cipriano wrote:
Well, it just started working. I did a "modprobe fuse" and another
gluster restart, and it started working.
But I would still appreciate any ideas about what I could look at
if/when this happens again.
:)
Glad that things started to work for you.
With 3.2.x versions, one of the ways to make sure we understand the
issue is by looking at the rebalance log file @
$logdir/etc-glusterd-mounts-<volname>.log (logdir is mostly
/var/log/glusterfs)
'modprobe fuse' helped because for rebalance operation we needed a
native glusterfs mount to happen, on top of which the rebalance logic
worked.
With 3.3.x releases, the dependency of 'fuse' for rebalance is gone as
rebalance happens as a separate process internal to glusterfs
translator. Also, the logfile to look at in 3.3.x releases will be
$logdir/<volname>-rebalance.log
Regards,
Amar
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
