Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

On Tue, 17 Apr 2018 at 10:06, Nithya Balachandran wrote: > That might be the reason. Perhaps the volfiles were not regenerated after > upgrading to the version with the fix. > Bumping up the op-version is necessary in this case as (AFAIK) the code was handling this based on

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

On 17 April 2018 at 10:03, Artem Russakovskii wrote: > I just remembered that I didn't run https://docs.gluster.org/ > en/v3/Upgrade-Guide/op_version/ for this test volume/box like I did for > the main production gluster, and one of these ops - either heal or the >

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

That might be the reason. Perhaps the volfiles were not regenerated after upgrading to the version with the fix. There is a workaround detailed in [2] for the time being (you will need to copy the shell script into the correct directory for your Gluster release). [2]

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

I just remembered that I didn't run https://docs.gluster.org/en/v3/Upgrade-Guide/op_version/ for this test volume/box like I did for the main production gluster, and one of these ops - either heal or the op-version, resolved the issue. I'm now seeing:

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

On Tue, Apr 17, 2018 at 9:59 AM, Nithya Balachandran wrote: > Ok, it looks like the same problem. > > > @Amar, this fix is supposed to be in 4.0.1. Is it possible to regenerate > the volfiles to fix this? > Yes, regenerating volfiles should fix it. Should we try a volume

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

Ok, it looks like the same problem. @Amar, this fix is supposed to be in 4.0.1. Is it possible to regenerate the volfiles to fix this? Regards, Nithya On 17 April 2018 at 09:57, Artem Russakovskii wrote: > pylon:/var/lib/glusterd/vols/dev_apkmirror_data # ack

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

To clarify, I was on 3.13.2 previously, recently updated to 4.0.1, and the bug seems to persist in 4.0.1. Sincerely, Artem -- Founder, Android Police , APK Mirror , Illogical Robot LLC beerpla.net | +ArtemRussakovskii

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

pylon:/var/lib/glusterd/vols/dev_apkmirror_data # ack shared-brick-count dev_apkmirror_data.pylon.mnt-pylon_block3-dev_apkmirror_data.vol 3:option shared-brick-count 3 dev_apkmirror_data.pylon.mnt-pylon_block2-dev_apkmirror_data.vol 3:option shared-brick-count 3

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

Hi Artem, Was the volume size correct before the bricks were expanded? This sounds like [1] but that should have been fixed in 4.0.0. Can you let us know the values of shared-brick-count in the files in /var/lib/glusterd/vols/dev_apkmirror_data/ ? [1]

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

Hi Nithya, I'm on Gluster 4.0.1. I don't think the bricks were smaller before - if they were, maybe 20GB because Linode's minimum is 20GB, then I extended them to 25GB, resized with resize2fs as instructed, and rebooted many times over since. Yet, gluster refuses to see the full disk size.

Re: [Gluster-users] Getting glusterfs to expand volume size to brick size

What version of Gluster are you running? Were the bricks smaller earlier? Regards, Nithya On 15 April 2018 at 00:09, Artem Russakovskii wrote: > Hi, > > I have a 3-brick replicate volume, but for some reason I can't get it to > expand to the size of the bricks. The bricks

[Gluster-users] Getting glusterfs to expand volume size to brick size

Hi, I have a 3-brick replicate volume, but for some reason I can't get it to expand to the size of the bricks. The bricks are 25GB, but even after multiple gluster restarts and remounts, the volume is only about 8GB. I believed I could always extend the bricks (we're using Linode block storage,