I'm using it in real-world production, lot of small files (apache webroot mounts mostly). I've seen a bunch of split-brain and self-heal failing when I first did the switch. After I removed and recreated the dirs it seemed to be fine for about a week now; yeah not long, I know. I 2nd the notion that it'd be nice to see a list of what files/dirs gluster thinks is out of sync or can't heal. Right now you gotta go diving into the logs. I'm actually thinking of downgrading to 3.1.3 from 3.2.0. Wonder if I'd have any ill-effects on the volume with a simple rpm downgrade and daemon restart. -Tony --------------------------- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abiacco at formatdynamics.com http://www.formatdynamics.com <http://www.formatdynamics.com/> From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of paul simpson Sent: Wednesday, May 18, 2011 8:05 AM To: Whit Blauvelt Cc: gluster-users at gluster.org Subject: Re: gluster 3.2.0 - totally broken? hi guys, we're using 3.1.3 and i'm not moving off it. i totally agree with stephans comments: the gluster devs *need* to concentrate on stability before adding any new features. it seems gluster dev is sales driven - not tech focused. we need less new buzz words - and more solid foundations. gluster is a great idea - but is in danger of falling short and failing if the current trajectory is now altered. greater posix compatibility (permissions, NLM locking) should be a perquisite for an NFS server. hell, the documentation is terrible; it's hard for us users to contribute to the community when we are groping around in the dark too. question : is anyone using 3.2 in a real world production situation? regards to all, -paul On 18 May 2011 14:54, Whit Blauvelt <whit.gluster at transpect.com> wrote:
