[Labs-l] NFS issues, please deploy fire

[Damian Zaremba]

On 14/09/2012 17:16, Ryan Lane wrote:
> Are there still issues with the version of fluster we upgraded to
> recently? It's still not usable for MySQL, but I haven't heard reports
> of bugs otherwise.
>
Aside from the known issues with MySQL I've not seen any issues with
gluster on project storage.

On 14/09/2012 08:24, Petr Bena wrote:
> Actually, there are issues with gluster which isn't much better, so
> any alternative to gluster or nfs would be nice
While there are issues with gluster (such as the mysql ones) it's at
least redundant and not going to run out of space rapidly.

Ceph would be really awesome to try, but as far as I know it's not had
any wide spread usage with open feedback/stats on performance.

Aside from the nfs instance being rather hammered on cpu/sluggish (which
will probably only get worse as more people use it), if it dies then
logins are broken for everyone.

I wouldn't be surprised if there is still 'production' stuff running
from there rather than project storage, combined with work-in-progress
stuff hovering around people's home dirs it's potentially a mess and a
chunk of lost data/time/effort.

Yes people should take backups, use version control etc, but I think we
should at least attempt to provide redundancy where possible (gluster)
and minimize impact for end users when things break (which is going to
happen at some point, especially when people are involved).

Things breaking/disappearing/being slow just makes people go elsewhere,
which breaks the community up and drives everything in the opposite
direction to where it should be heading.

Just my 2¢.

Damian