Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.
That's not true for EL-based systems as they have 'glusterfsd.service' which on shutdown kills all gluster brick processes. Best Regards,Strahil Nikolov On Tue, Feb 6, 2024 at 9:21, Diego Zuccato wrote: Just a notice: bricks processes not being terminated prevents a simple "reboot" (or "shutdown -r now", or an automated shutdown initiated by UPS) to complete: you're left with most daemons (including sshd) terminated and a machine that's neither shutting down nor returning to normal operations and the only option is unclean shutdown. Diego Il 05/02/2024 19:22, Anant Saraswat ha scritto: > Hi Hu, > > Yes, I have used the "stop-all-gluster-processes.sh" after systemctl stop. > > I consider "stop-all-gluster-processes.sh" as the last resort to kill > all the remaining gluster processes. Do you use it primarily to stop the > gluster? > > Thanks, > Anant > > Get Outlook for iOS <https://aka.ms/o0ukef> > > *From:* Hu Bert > *Sent:* Monday, February 5, 2024 6:15 PM > *To:* Anant Saraswat > *Cc:* gluster-users@gluster.org > *Subject:* Re: [Gluster-users] Challenges with Replicated Gluster volume > after stopping Gluster on any node. > > *EXTERNAL: Do not click links or open attachments if you do not > recognize the sender.* > > Hi, > normally, when we shut down or reboot one of the (server) nodes, we call > the "stop-all-gluster-processes.sh" script. But i think you did that, right? > > > Best regards, > Hubert > > > Am Mo., 5. Feb. 2024 um 13:35 Uhr schrieb Anant Saraswat > mailto:anant.saras...@techblue.co.uk>>: > > Hello Everyone, > > We have a replicated Gluster volume with three nodes, and we face a > strange issue whenever we need to restart one of the nodes in this > cluster. > > As per my understanding, if we shut down one node, the Gluster mount > should smoothly connect to another remaining Gluster server and > shouldn't create any issues. > > In our setup, when we stop Gluster on any of the nodes, we mostly > get the error 'Transport endpoint is not connected' on the clients. > When we run the commands to check the connected clients on the > Gluster server, we get the following error: > > gluster volume status tier1data clients > FAILED: Commit failed on master1. Error: Unable to decode brick op > response. > > Could anyone recommend a potential solution for this? > > Thanks, > Anant > > > Anant Saraswat > > DevOps Lead > > IT | Technology Blueprint Ltd. > > > mobilePhone > > +44-8450047142 (5020) | > +91-9818761614 > emailAddress > > anant.saras...@techblue.co.uk <mailto:anant.saras...@techblue.co.uk> > website > > https://www.technologyblueprint.co.uk > ><https://urldefense.com/v3/__https://www.technologyblueprint.co.uk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4EZVhUf-$> > address > > Salisbury House, Station Road, Cambridge, Cambridgeshire, CB1 2LA > > DISCLAIMER: This email and any files transmitted with it are > confidential and intended solely for the use of the individual or > entity to whom they are addressed. If you have received this email > in error, please notify the sender. This message contains > confidential information and is intended only for the individual > named. If you are not the named addressee, you should not > disseminate, distribute or copy this email. Please notify the sender > immediately by email if you have received this email by mistake and > delete this email from your system. > > If you are not the intended recipient, you are notified that > disclosing, copying, distributing or taking any action in reliance > on the contents of this information is strictly prohibited. Thanks > for your cooperation. > > > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://meet.google.com/cpu-eiue-hvk > ><https://urldefense.com/v3/__https://meet.google.com/cpu-eiue-hvk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4BWhreAq$> > Gluster-users mailing list > Gluster-users@gluster.org <mailto:Gluster-users@gluster.org> > https://lists.gluster.org/mailman/listinfo/gluster-users > ><https://urldefense.com/v3/__https://lists.gluster.org/mailman/listinfo/glust
Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.
Thanks Hubert, I will try to run the script initially for future reference. From: Hu Bert Sent: 07 February 2024 6:55 AM To: Anant Saraswat Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node. EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Hi Anant, e.g. if i reboot a gluster server this is the only script that i use - i don't use systemctl at all. Best regards, Hubert Am Mo., 5. Feb. 2024 um 19:22 Uhr schrieb Anant Saraswat mailto:anant.saras...@techblue.co.uk>>: Hi Hu, Yes, I have used the "stop-all-gluster-processes.sh" after systemctl stop. I consider "stop-all-gluster-processes.sh" as the last resort to kill all the remaining gluster processes. Do you use it primarily to stop the gluster? Thanks, Anant Get Outlook for iOS<https://urldefense.com/v3/__https://aka.ms/o0ukef__;!!I_DbfM1H!BYCizEp5lAOkvEcZIUL3Wn4Or8R1VEMAH-eXUdiVu48E0tEp1NV3fDc-BPReJbkXnzdTxuOLBD_AU2tvFYNZF5FiY60P$> From: Hu Bert mailto:revi...@googlemail.com>> Sent: Monday, February 5, 2024 6:15 PM To: Anant Saraswat mailto:anant.saras...@techblue.co.uk>> Cc: gluster-users@gluster.org<mailto:gluster-users@gluster.org> mailto:gluster-users@gluster.org>> Subject: Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node. EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Hi, normally, when we shut down or reboot one of the (server) nodes, we call the "stop-all-gluster-processes.sh" script. But i think you did that, right? Best regards, Hubert Am Mo., 5. Feb. 2024 um 13:35 Uhr schrieb Anant Saraswat mailto:anant.saras...@techblue.co.uk>>: Hello Everyone, We have a replicated Gluster volume with three nodes, and we face a strange issue whenever we need to restart one of the nodes in this cluster. As per my understanding, if we shut down one node, the Gluster mount should smoothly connect to another remaining Gluster server and shouldn't create any issues. In our setup, when we stop Gluster on any of the nodes, we mostly get the error 'Transport endpoint is not connected' on the clients. When we run the commands to check the connected clients on the Gluster server, we get the following error: gluster volume status tier1data clients FAILED: Commit failed on master1. Error: Unable to decode brick op response. Could anyone recommend a potential solution for this? Thanks, Anant Anant Saraswat DevOps Lead IT | Technology Blueprint Ltd. +44-8450047142 (5020) | +91-9818761614 anant.saras...@techblue.co.uk<mailto:anant.saras...@techblue.co.uk> https://www.technologyblueprint.co.uk<https://urldefense.com/v3/__https://www.technologyblueprint.co.uk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4EZVhUf-$> Salisbury House, Station Road, Cambridge, Cambridgeshire, CB1 2LA DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk<https://urldefense.com/v3/__https://meet.google.com/cpu-eiue-hvk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4BWhreAq$> Gluster-users mailing list Gluster-users@gluster.org<mailto:Gluster-users@gluster.org> https://lists.gluster.org/mailman/listinfo/gluster-users<https://urldefense.com/v3/__https://lists.gluster.org/mailman/listinfo/gluster-users__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4IQKpS1U$> DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email
Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.
Hi Anant, e.g. if i reboot a gluster server this is the only script that i use - i don't use systemctl at all. Best regards, Hubert Am Mo., 5. Feb. 2024 um 19:22 Uhr schrieb Anant Saraswat < anant.saras...@techblue.co.uk>: > Hi Hu, > > Yes, I have used the "stop-all-gluster-processes.sh" after systemctl stop. > > I consider "stop-all-gluster-processes.sh" as the last resort to kill all > the remaining gluster processes. Do you use it primarily to stop the > gluster? > > Thanks, > Anant > > Get Outlook for iOS <https://aka.ms/o0ukef> > -- > *From:* Hu Bert > *Sent:* Monday, February 5, 2024 6:15 PM > *To:* Anant Saraswat > *Cc:* gluster-users@gluster.org > *Subject:* Re: [Gluster-users] Challenges with Replicated Gluster volume > after stopping Gluster on any node. > > > *EXTERNAL: Do not click links or open attachments if you do not recognize > the sender.* > Hi, > normally, when we shut down or reboot one of the (server) nodes, we call > the "stop-all-gluster-processes.sh" script. But i think you did that, right? > > > Best regards, > Hubert > > > Am Mo., 5. Feb. 2024 um 13:35 Uhr schrieb Anant Saraswat < > anant.saras...@techblue.co.uk>: > >> Hello Everyone, >> >> We have a replicated Gluster volume with three nodes, and we face a >> strange issue whenever we need to restart one of the nodes in this cluster. >> >> As per my understanding, if we shut down one node, the Gluster mount >> should smoothly connect to another remaining Gluster server and shouldn't >> create any issues. >> >> In our setup, when we stop Gluster on any of the nodes, we mostly get the >> error 'Transport endpoint is not connected' on the clients. When we run the >> commands to check the connected clients on the Gluster server, we get the >> following error: >> >> gluster volume status tier1data clients >> FAILED: Commit failed on master1. Error: Unable to decode brick op >> response. >> >> Could anyone recommend a potential solution for this? >> >> Thanks, >> Anant >> >> Anant Saraswat >> >> DevOps Lead >> >> IT | Technology Blueprint Ltd. >> [image: mobilePhone] >> +44-8450047142 (5020) <+44-8450047142%20(5020)> | +91-9818761614 >> >> [image: emailAddress] >> anant.saras...@techblue.co.uk >> >> [image: website] >> https://www.technologyblueprint.co.uk >> <https://urldefense.com/v3/__https://www.technologyblueprint.co.uk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4EZVhUf-$> >> >> [image: address] >> Salisbury House, Station Road, Cambridge, Cambridgeshire, CB1 2LA >> >> DISCLAIMER: This email and any files transmitted with it are confidential >> and intended solely for the use of the individual or entity to whom they >> are addressed. If you have received this email in error, please notify the >> sender. This message contains confidential information and is intended only >> for the individual named. If you are not the named addressee, you should >> not disseminate, distribute or copy this email. Please notify the sender >> immediately by email if you have received this email by mistake and delete >> this email from your system. >> >> If you are not the intended recipient, you are notified that disclosing, >> copying, distributing or taking any action in reliance on the contents of >> this information is strictly prohibited. Thanks for your cooperation. >> >> >> >> >> Community Meeting Calendar: >> >> Schedule - >> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC >> Bridge: https://meet.google.com/cpu-eiue-hvk >> <https://urldefense.com/v3/__https://meet.google.com/cpu-eiue-hvk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4BWhreAq$> >> Gluster-users mailing list >> Gluster-users@gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users >> <https://urldefense.com/v3/__https://lists.gluster.org/mailman/listinfo/gluster-users__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4IQKpS1U$> >> > DISCLAIMER: This email and any files transmitted with it are confidential > and intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error, please notify the > sender. This message contains confidential information and is intended only > for the individual named. If you are not the
Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.
Just a notice: bricks processes not being terminated prevents a simple "reboot" (or "shutdown -r now", or an automated shutdown initiated by UPS) to complete: you're left with most daemons (including sshd) terminated and a machine that's neither shutting down nor returning to normal operations and the only option is unclean shutdown. Diego Il 05/02/2024 19:22, Anant Saraswat ha scritto: Hi Hu, Yes, I have used the "stop-all-gluster-processes.sh" after systemctl stop. I consider "stop-all-gluster-processes.sh" as the last resort to kill all the remaining gluster processes. Do you use it primarily to stop the gluster? Thanks, Anant Get Outlook for iOS <https://aka.ms/o0ukef> *From:* Hu Bert *Sent:* Monday, February 5, 2024 6:15 PM *To:* Anant Saraswat *Cc:* gluster-users@gluster.org *Subject:* Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node. *EXTERNAL: Do not click links or open attachments if you do not recognize the sender.* Hi, normally, when we shut down or reboot one of the (server) nodes, we call the "stop-all-gluster-processes.sh" script. But i think you did that, right? Best regards, Hubert Am Mo., 5. Feb. 2024 um 13:35 Uhr schrieb Anant Saraswat mailto:anant.saras...@techblue.co.uk>>: Hello Everyone, We have a replicated Gluster volume with three nodes, and we face a strange issue whenever we need to restart one of the nodes in this cluster. As per my understanding, if we shut down one node, the Gluster mount should smoothly connect to another remaining Gluster server and shouldn't create any issues. In our setup, when we stop Gluster on any of the nodes, we mostly get the error 'Transport endpoint is not connected' on the clients. When we run the commands to check the connected clients on the Gluster server, we get the following error: gluster volume status tier1data clients FAILED: Commit failed on master1. Error: Unable to decode brick op response. Could anyone recommend a potential solution for this? Thanks, Anant Anant Saraswat DevOps Lead IT | Technology Blueprint Ltd. mobilePhone +44-8450047142 (5020) | +91-9818761614 emailAddress anant.saras...@techblue.co.uk <mailto:anant.saras...@techblue.co.uk> website https://www.technologyblueprint.co.uk <https://urldefense.com/v3/__https://www.technologyblueprint.co.uk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4EZVhUf-$> address Salisbury House, Station Road, Cambridge, Cambridgeshire, CB1 2LA DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk <https://urldefense.com/v3/__https://meet.google.com/cpu-eiue-hvk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4BWhreAq$> Gluster-users mailing list Gluster-users@gluster.org <mailto:Gluster-users@gluster.org> https://lists.gluster.org/mailman/listinfo/gluster-users <https://urldefense.com/v3/__https://lists.gluster.org/mailman/listinfo/gluster-users__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4IQKpS1U$> DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the inten
Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.
Hi Hu, Yes, I have used the "stop-all-gluster-processes.sh" after systemctl stop. I consider "stop-all-gluster-processes.sh" as the last resort to kill all the remaining gluster processes. Do you use it primarily to stop the gluster? Thanks, Anant Get Outlook for iOS<https://aka.ms/o0ukef> From: Hu Bert Sent: Monday, February 5, 2024 6:15 PM To: Anant Saraswat Cc: gluster-users@gluster.org Subject: Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node. EXTERNAL: Do not click links or open attachments if you do not recognize the sender. Hi, normally, when we shut down or reboot one of the (server) nodes, we call the "stop-all-gluster-processes.sh" script. But i think you did that, right? Best regards, Hubert Am Mo., 5. Feb. 2024 um 13:35 Uhr schrieb Anant Saraswat mailto:anant.saras...@techblue.co.uk>>: Hello Everyone, We have a replicated Gluster volume with three nodes, and we face a strange issue whenever we need to restart one of the nodes in this cluster. As per my understanding, if we shut down one node, the Gluster mount should smoothly connect to another remaining Gluster server and shouldn't create any issues. In our setup, when we stop Gluster on any of the nodes, we mostly get the error 'Transport endpoint is not connected' on the clients. When we run the commands to check the connected clients on the Gluster server, we get the following error: gluster volume status tier1data clients FAILED: Commit failed on master1. Error: Unable to decode brick op response. Could anyone recommend a potential solution for this? Thanks, Anant Anant Saraswat DevOps Lead IT | Technology Blueprint Ltd. [mobilePhone] +44-8450047142 (5020) | +91-9818761614 [emailAddress] anant.saras...@techblue.co.uk<mailto:anant.saras...@techblue.co.uk> [website] https://www.technologyblueprint.co.uk<https://urldefense.com/v3/__https://www.technologyblueprint.co.uk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4EZVhUf-$> [address] Salisbury House, Station Road, Cambridge, Cambridgeshire, CB1 2LA DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk<https://urldefense.com/v3/__https://meet.google.com/cpu-eiue-hvk__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4BWhreAq$> Gluster-users mailing list Gluster-users@gluster.org<mailto:Gluster-users@gluster.org> https://lists.gluster.org/mailman/listinfo/gluster-users<https://urldefense.com/v3/__https://lists.gluster.org/mailman/listinfo/gluster-users__;!!I_DbfM1H!HlVD8KfD8301Uq0Lq9EeyrI7mMGdgXcE2IwOS99fuppfYoCIBGTz0MqYAR-oRGuHhwXpq9lDRCX86lHUGepk4IQKpS1U$> DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Thanks for your cooperation. Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Challenges with Replicated Gluster volume after stopping Gluster on any node.
Hi, normally, when we shut down or reboot one of the (server) nodes, we call the "stop-all-gluster-processes.sh" script. But i think you did that, right? Best regards, Hubert Am Mo., 5. Feb. 2024 um 13:35 Uhr schrieb Anant Saraswat < anant.saras...@techblue.co.uk>: > Hello Everyone, > > We have a replicated Gluster volume with three nodes, and we face a > strange issue whenever we need to restart one of the nodes in this cluster. > > As per my understanding, if we shut down one node, the Gluster mount > should smoothly connect to another remaining Gluster server and shouldn't > create any issues. > > In our setup, when we stop Gluster on any of the nodes, we mostly get the > error 'Transport endpoint is not connected' on the clients. When we run the > commands to check the connected clients on the Gluster server, we get the > following error: > > gluster volume status tier1data clients > FAILED: Commit failed on master1. Error: Unable to decode brick op > response. > > Could anyone recommend a potential solution for this? > > Thanks, > Anant > > Anant Saraswat > > DevOps Lead > > IT | Technology Blueprint Ltd. > [image: mobilePhone] > +44-8450047142 (5020) <+44-8450047142%20(5020)> | +91-9818761614 > > [image: emailAddress] > anant.saras...@techblue.co.uk > > [image: website] > https://www.technologyblueprint.co.uk > > [image: address] > Salisbury House, Station Road, Cambridge, Cambridgeshire, CB1 2LA > > DISCLAIMER: This email and any files transmitted with it are confidential > and intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error, please notify the > sender. This message contains confidential information and is intended only > for the individual named. If you are not the named addressee, you should > not disseminate, distribute or copy this email. Please notify the sender > immediately by email if you have received this email by mistake and delete > this email from your system. > > If you are not the intended recipient, you are notified that disclosing, > copying, distributing or taking any action in reliance on the contents of > this information is strictly prohibited. Thanks for your cooperation. > > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://meet.google.com/cpu-eiue-hvk > Gluster-users mailing list > Gluster-users@gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users > Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
