search for: glusterdocs

...op-version? > > He is not changing mayor versions, just a small step from 3.8.12 to > 3.8.13. Corruption should not be happening. > For some reason 3.8 upgrade guide is not where it is supposed to be. We highly recommend upgrading servers ahead of clients. https://github.com/nixpanic/glusterdocs/commit/f6d48dc17f2cb6ee4680e372520ec3358641b2bc I think at some point it is better to make this mandatory. Without a predefined way of upgrading, it is very difficult to fix bugs in backward compatible manner. I am not sure why the corruption happened either :-(. Pavel, could you give log files m...

...s hosted on >> > RTD. >> > >> > [1]: https://docs.readthedocs.io/en/latest/canonical.html >> >> So , seems TLS certificate is wrong, should we correct the link to be >> http for now ? > > So I opened a few PR/review: > https://github.com/gluster/glusterdocs/pull/259 > > https://review.gluster.org/#/c/18182/ > > https://github.com/gluster/glusterweb/pull/148 > > > -- > Michael Scherer > Sysadmin, Community Infrastructure and Platform, OSAS > > > _______________________________________________ > Gluster-devel maili...

On Thu, Jun 29, 2017 at 7:48 PM, Paolo Margara <paolo.margara at polito.it> wrote: > Hi Pranith, > > I'm using this guide https://github.com/nixpanic/glusterdocs/blob/ > f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md > > Definitely my fault, but I think that is better to specify somewhere that > restarting the service is not enough simply because in many other case, > with other services, is sufficient. > The step...

...we've had with copies of our docs hosted on > > RTD. > > > > [1]: https://docs.readthedocs.io/en/latest/canonical.html > > So , seems TLS certificate is wrong, should we correct the link to be > http for now ? So I opened a few PR/review: https://github.com/gluster/glusterdocs/pull/259 https://review.gluster.org/#/c/18182/ https://github.com/gluster/glusterweb/pull/148 -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signat...

Hi Pranith, I'm using this guide https://github.com/nixpanic/glusterdocs/blob/f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md Definitely my fault, but I think that is better to specify somewhere that restarting the service is not enough simply because in many other case, with other services, is sufficient. Now I'm restarting every brick pr...

...He is not changing mayor versions, just a small step from 3.8.12 to >> 3.8.13. Corruption should not be happening. > > > For some reason 3.8 upgrade guide is not where it is supposed to be. > We highly recommend upgrading servers ahead of clients. > https://github.com/nixpanic/glusterdocs/commit/f6d48dc17f2cb6ee4680e372520ec3358641b2bc > > I think at some point it is better to make this mandatory. Without a > predefined way of upgrading, it is very difficult to fix bugs in backward > compatible manner. > > I am not sure why the corruption happened either :-(. Pavel...

Le mercredi 30 ao?t 2017 ? 12:11 +0530, Nigel Babu a ?crit?: > Hello, > > To reduce confusion, we've setup docs.gluster.org pointing to > gluster.readthedocs.org. Both URLs will continue to work for the > forseeable > future. > > Please update any references that you control to point to > docs.gluster.org. At > some point in the distant future, we will switch to

...show rebalance status. Not sure why you're seeing it. Adding Nithya for help. > > Regarding the patch to the documentation: absolutely! Let me just get > my Gluster back in order after my confusing upgrade last month. :P Great. Please send the PR for the https://github.com/gluster/glusterdocs/ project. I think docs/Administrator Guide/Managing Volumes.md is the file that needs to be updated. -Ravi > > Thanks, > > On Tue, Jun 11, 2019 at 7:32 PM Ravishankar N <ravishankar at redhat.com > <mailto:ravishankar at redhat.com>> wrote: > > > On 11/0...

Hi all, Over the years I have been using the same ports in my firewall for gluster 49152-49251 ( I know a bit too many ports but local network with limited access) Today I upgraded from version 9 to version 10 and it finally went well until I ran: gluster volume heal my-vol info summary I got the answer: Status: Transport endpoint is not connected I realized that glusterfsd was using 50000+

...> > > >> > [1]: https://docs.readthedocs.io/en/latest/canonical.html > >> > >> So , seems TLS certificate is wrong, should we correct the link to be > >> http for now ? > > > > So I opened a few PR/review: > > https://github.com/gluster/glusterdocs/pull/259 > > > > https://review.gluster.org/#/c/18182/ > > > > https://github.com/gluster/glusterweb/pull/148 > > > > > > -- > > Michael Scherer > > Sysadmin, Community Infrastructure and Platform, OSAS > > > > > > ____________...

...17 16:27, Pranith Kumar Karampuri ha scritto: > > > On Thu, Jun 29, 2017 at 7:48 PM, Paolo Margara > <paolo.margara at polito.it <mailto:paolo.margara at polito.it>> wrote: > > Hi Pranith, > > I'm using this guide > https://github.com/nixpanic/glusterdocs/blob/f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md > <https://github.com/nixpanic/glusterdocs/blob/f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md> > > Definitely my fault, but I think that is better to specify > some...

Hi Rowland, I ment thay I removed some extra options from Felix settings - as they are for Samba in DC , and my setup is a Stand-alone samba. @Anoop, so this is expected ? I will check the documentation and follow up. Maybe I can optimize the Gluster documentation and update that? Best Regards, Strahil Nikolov ?? 1 ??? 2020 ?. 21:07:26 GMT+03:00, Rowland penny via samba <samba at

I propose to present on one or more of the following topics: * NFS-Ganesha Architecture, Roadmap, and Status * Architecture of the High Availability Solution for Ganesha and Samba - detailed walk through and demo of current implementation - difference between the current and storhaug implementations * High Level Overview of autoconf/automake/libtool configuration (I gave a presentation in BLR

> > You should first upgrade servers and then clients. New servers can > understand old clients, but it is not easy for old servers to understand new > clients in case it started doing something new. But isn't that the reason op-version exists? So that regardless of client/server mix, nobody tries to do "new" things above the current op-version? He is not changing mayor

On Mon, Jul 10, 2017 at 10:33 PM, Mahdi Adnan <mahdi.adnan at outlook.com> wrote: > I upgraded from 3.8.12 to 3.8.13 without issues. > > Two replicated volumes with online update, upgraded clients first and > followed by servers upgrade, "stop glusterd, pkill gluster*, update > gluster*, start glusterd, monitor healing process and logs, after > completion proceed to

Hi everyone, I've read on the gluster & redhat documentation, that it seems recommended to use XFS over LVM before creating & using gluster volumes. Sources : https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/Formatting_and_Mounting_Bricks.html http://gluster.readthedocs.io/en/latest/Administrator%20Guide/Setting%20Up%20Volumes/ My point is :

On 09/18/2017 09:22 PM, ABHISHEK PALIWAL wrote: > Any suggestion would be appreciated... > > On Sep 18, 2017 15:05, "ABHISHEK PALIWAL" <abhishpaliwal at gmail.com > <mailto:abhishpaliwal at gmail.com>> wrote: > > Any quick suggestion.....? > > On Mon, Sep 18, 2017 at 1:50 PM, ABHISHEK PALIWAL > <abhishpaliwal at gmail.com

Paolo, Which document did you follow for the upgrade? We can fix the documentation if there are any issues. On Thu, Jun 29, 2017 at 2:07 PM, Ravishankar N <ravishankar at redhat.com> wrote: > On 06/29/2017 01:08 PM, Paolo Margara wrote: > > Hi all, > > for the upgrade I followed this procedure: > > - put node in maintenance mode (ensure no client are active)

On 06/29/2017 01:08 PM, Paolo Margara wrote: > > Hi all, > > for the upgrade I followed this procedure: > > * put node in maintenance mode (ensure no client are active) > * yum versionlock delete glusterfs* > * service glusterd stop > * yum update > * systemctl daemon-reload > * service glusterd start > * yum versionlock add glusterfs* > *

On Mon, Jun 26, 2017 at 7:40 PM, Pat Haley <phaley at mit.edu> wrote: > > Hi All, > > Decided to try another tests of gluster mounted via FUSE vs gluster > mounted via NFS, this time using the software we run in production (i.e. > our ocean model writing a netCDF file). > > gluster mounted via NFS the run took 2.3 hr > > gluster mounted via FUSE: the run took