More need to validate tcmalloc as malloc is very very common pattern across the codebase of GlusterFS.

• http://goog-perftools.sourceforge.net/doc/tcmalloc.html
• https://github.com/gperftools/gperftools

Kind of issue

Feature request

Observed behavior

The changes made in PRs #1287 and #1310 adjust the total usable size of a block hosting volume by reserving some of the raw capacity as overhead. Thus if you create a block hosting volume of 100GiB then a block volume of 100GiB is too large to be hosted in that volume.

Expected/desired behavior

What I suggest is the behav

Hello,
In a situation of deploying Windows container with azure batch shipyard, there are not many samples for Windows container users. currently these YAML samples are mostly for Linux users.
It would be nice to add more samples and documentation for windows container user so that the users do not get confused with some gaps between operating systems in configuration.

I found two samples whi

Originally created by Paul Cuzner

In the current plan, the snap create syntax mandates the admin provides a name for the snapshot. Whilst having the ability to supply a name is great, it should not be mandated and should have a name created by default if one is not supplied.

For example

<volume_name>_YYYYddMM_hhMM

Adopting this approach will mean snapshots by default get sensible names

To be able to provide more details when someone create an issue as it what will happen every time gluster failed to mount.

For proof : https://github.com/sapk/docker-volume-gluster/issues?utf8=%E2%9C%93&q=exit+status+1

• try to ping/resolve each clusters membres to be sure that it resolve as it is common error.

Default docker nfs support doesn't create the needed directory for the volume (for example by volume name inside of the base nfs share directory).
Is it supported with your plugin?