Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with GlusterFS #748

Open
NdK73 opened this issue Jul 28, 2020 · 1 comment
Open

Problem with GlusterFS #748

NdK73 opened this issue Jul 28, 2020 · 1 comment

Comments

@NdK73
Copy link

NdK73 commented Jul 28, 2020

Hi.

I just fought with DiskSpaceCollector because it didn't report the disk usage for a fuse.glusterfs mounted directory.

The first problem (trivial) was that in the default config "gluster" is given instead of "fuse.gluster" . No problem, corrected.

But even after correction the metrics were silently dropped.
I found that the if at diskspace.py:153 assumes the "device" starts with a '/'. Too bad, usually mountpoints for gluster use the format
srv1[,srv2]:volume_name

It's possible to use
/srv1[,srv2]:volume_name
(with a leading '/') but I think it's quite uncommon.
I made that if a no-op (adding as first condition "(1==1) or" ), but I think it could be better to consider the GlusterFS case and/or give a meaningful message stating why that mountpoint is getting discarded.

HIH

@shortdudey123
Copy link
Member

Is this still occurring with master? By reading the collector code, it looks like it should be working. If not, can you give sanitized output of /proc/mounts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants