Re: Graceful shutdown doesn't stop all Gluster processes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Basically the lvm operations on the iSCSI target are online, and then on the client rescan the lun: 'iscsiadm -m node --targetname target_name -R and then just extend the FS.
Of course, test the procedure before doing it in production.

Why do you use glusterFS on iSCSI ? You can have a shared file system on the same lun and mounted on multiple nodes.

Gluster is supposed to be used with local disks in order to improve resilience and scale to massive sizes.

Best Regards,
Strahil Nikolov

On Mon, Feb 26, 2024 at 11:37, Anant Saraswat
<anant.saraswat@xxxxxxxxxxxxxx> wrote:
Hi Strahil,

In our setup, the Gluster brick comes from an iSCSI SAN storage and is then used as a brick on the Gluster server. To extend the brick, we stop the Gluster server, extend the logical volume (LV) on the SAN server, resize it on the host, mount the brick with the extended size, and finally start the Gluster server.

Please let me know if this process can be optimized, I will be happy to do so.

Many thanks,

From: Strahil Nikolov <hunter86_bg@xxxxxxxxx>
Sent: 24 February 2024 12:33 PM
To: Anant Saraswat <anant.saraswat@xxxxxxxxxxxxxx>
Cc: gluster-users@xxxxxxxxxxx <gluster-users@xxxxxxxxxxx>
Subject: Re: Graceful shutdown doesn't stop all Gluster processes
EXTERNAL: Do not click links or open attachments if you do not recognize the sender.

Hi Anant,

why would you need to shutdown a brick to expand it ? This is an online operation.

Best Regards,
Strahil Nikolov

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
Gluster-users mailing list

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux