Re: [Gluster-users] Upgrading from glusterfs 3.12.15 on CentOS7 to gluster-6
Hi, On Fri, Oct 02, 2020 at 07:59:57PM +, Strahil Nikolov wrote: > You can enable the CentOS Storage SIG repos for gluster. > > #yum search centos-release-gluster > > N/S matched: > centos-release-gluster > > centos-release-gluster-legacy.noarch : Disable unmaintained Gluster > repositories from the CentOS Storage SIG > centos-release-gluster40.x86_64 : Gluster 4.0 (Short Term Stable) packages > from the CentOS Storage SIG repository > centos-release-gluster41.noarch : Gluster 4.1 (Long Term Stable) packages > from the CentOS Storage SIG repository > centos-release-gluster5.noarch : Gluster 5 packages from the CentOS Storage > SIG repository > centos-release-gluster6.noarch : Gluster 6 packages from the CentOS Storage > SIG repository > centos-release-gluster7.noarch : Gluster 7 packages from the CentOS Storage > SIG repository > Yep, as i'm already using the centos gluster rpms for 3.12, that's what I'll do for the newer version aswell. > > As far as I know 3.12.15 allows you to upgrade without downtime to higher > versions of Gluster. As far as I remember I upgraded from that version to 5.5 > some time ago, but should also work with 6.X ... > Ok, thanks. Anyone else, did you upgrade from gluster 3.12 to 6.x? How did it go? Any known issues? I guess I'll have to test it and see how it goes.. :) Thanks, -- Pasi > > Best Regards, > Strahil Nikolov > > ?? ??, 2 2020 ??., 19:19:38 ??+3, Pasi > Kärkkäinen : > > Hello list, > > I have a system running old CentOS 7.5 + glusterfs 3.12.15 from > centos-gluster312 repo. > Anyone here on the list who upgraded such a setup to a later glusterfs > release, for example to glusterfs 6.x? > > It seems I can't upgrade the CentOS7 base OS to newest version anymore > because later rhel7/CentOS7 releases contain glusterfs-6.0 client libraries > in the base repo, making "yum update" to fail due to dependency problems > between base repo and the installed gluster312 packages: > > yum output example: > > Error: Package: glusterfs-server-3.12.15-1.el7.x86_64 (@centos-gluster312) > Requires: glusterfs-cli = 3.12.15-1.el7 > Removing: glusterfs-cli-3.12.15-1.el7.x86_64 (@centos-gluster312) > glusterfs-cli = 3.12.15-1.el7 > Updated By: glusterfs-cli-6.0-29.el7.x86_64 (base) > glusterfs-cli = 6.0-29.el7 > > So I think I probably first need to upgrade from centos-gluster312 repo/rpms > to centos-gluster6 repo rpms, which includes the latest glusterfs-6.10 rpms, > which are newer than the glusterfs-6.0 rpms in the base OS, and that probably > fixes the dependency problems.. > > Any thoughts? Did anyone have the same problem? How did you solve it? > > How about experiences upgrading from glusterfs 3.12 to glusterfs 6.x in > general? How did it go? Any known problems? > (I know there was many issues earlier, but afaik many/most of those got fixed > in later glusterfs 6.x versions). > > > Thanks a lot, > > -- Pasi > Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Upgrading from glusterfs 3.12.15 on CentOS7 to gluster-6
Hello list, I have a system running old CentOS 7.5 + glusterfs 3.12.15 from centos-gluster312 repo. Anyone here on the list who upgraded such a setup to a later glusterfs release, for example to glusterfs 6.x? It seems I can't upgrade the CentOS7 base OS to newest version anymore because later rhel7/CentOS7 releases contain glusterfs-6.0 client libraries in the base repo, making "yum update" to fail due to dependency problems between base repo and the installed gluster312 packages: yum output example: Error: Package: glusterfs-server-3.12.15-1.el7.x86_64 (@centos-gluster312) Requires: glusterfs-cli = 3.12.15-1.el7 Removing: glusterfs-cli-3.12.15-1.el7.x86_64 (@centos-gluster312) glusterfs-cli = 3.12.15-1.el7 Updated By: glusterfs-cli-6.0-29.el7.x86_64 (base) glusterfs-cli = 6.0-29.el7 So I think I probably first need to upgrade from centos-gluster312 repo/rpms to centos-gluster6 repo rpms, which includes the latest glusterfs-6.10 rpms, which are newer than the glusterfs-6.0 rpms in the base OS, and that probably fixes the dependency problems.. Any thoughts? Did anyone have the same problem? How did you solve it? How about experiences upgrading from glusterfs 3.12 to glusterfs 6.x in general? How did it go? Any known problems? (I know there was many issues earlier, but afaik many/most of those got fixed in later glusterfs 6.x versions). Thanks a lot, -- Pasi Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Announcing Glusterfs release 3.12.13 (Long Term Maintenance)
On Tue, Aug 28, 2018 at 10:12:06AM +0530, Jiffin Tony Thottan wrote: > > > On Monday 27 August 2018 01:57 PM, Pasi Kärkkäinen wrote: > >Hi, > > > >On Mon, Aug 27, 2018 at 11:10:21AM +0530, Jiffin Tony Thottan wrote: > >>The Gluster community is pleased to announce the release of Gluster > >>3.12.13 (packages available at [1,2,3]). > >> > >>Release notes for the release can be found at [4]. > >> > >>Thanks, > >>Gluster community > >> > >>[1] [1]https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.13/ > >>[2] [2]https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12 > >>[3] [3]https://build.opensuse.org/project/subprojects/home:glusterfs > >>[4] Release notes: > >>[4]https://gluster.readthedocs.io/en/latest/release-notes/3.12.12/ > >> > >Hmm, I guess release-notes link should say > >https://gluster.readthedocs.io/en/latest/release-notes/3.12.13 instead.. but > >that page doesn't seem to exist (yet) ? > > It got fixed now :) > Great, thanks! -- Pasi > Thanks, > Jiffin > ___ Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Announcing Glusterfs release 3.12.13 (Long Term Maintenance)
Hi, On Mon, Aug 27, 2018 at 11:10:21AM +0530, Jiffin Tony Thottan wrote: >The Gluster community is pleased to announce the release of Gluster >3.12.13 (packages available at [1,2,3]). > >Release notes for the release can be found at [4]. > >Thanks, >Gluster community > >[1] [1]https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.13/ >[2] [2]https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12 >[3] [3]https://build.opensuse.org/project/subprojects/home:glusterfs >[4] Release notes: >[4]https://gluster.readthedocs.io/en/latest/release-notes/3.12.12/ > Hmm, I guess release-notes link should say https://gluster.readthedocs.io/en/latest/release-notes/3.12.13 instead.. but that page doesn't seem to exist (yet) ? Thanks, -- Pasi ___ Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] gluster 3.7 healing errors (no data available, buf->ia_gfid is null)
On Thu, Sep 22, 2016 at 07:20:26PM +0530, Pranith Kumar Karampuri wrote: >On Thu, Sep 22, 2016 at 12:51 PM, Ravishankar N ><[1]ravishan...@redhat.com> wrote: > > On 09/22/2016 12:38 PM, Pasi KÀrkkÀinen wrote: > >On Thu, Sep 22, 2016 at 09:58:25AM +0530, Ravishankar N wrote: > > On 09/21/2016 10:54 PM, Pasi KÀrkkÀinen wrote: > >Let's see. > ># getfattr -m . -d -e hex /bricks/vol1/brick1/foo >getfattr: Removing leading '/' from absolute path names ># file: bricks/vol1/brick1/foo > > security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000 > >So hmm.. no trusted.gfid it seems.. is that perhaps because this >node was down when the file was created? > > No, even if that were the case, the gfid should have been set while > healing the file to this node. > Can you try doing a setfattr -n trusted.gfid -v > 0xc1ca778ed2af4828b981171c0c5bd45e on the file. and launch heal > again? > What about the .glusterfs hardlink- does that exist? > >It seems there's no hardlink.. nothing in >/bricks/vol1/brick1/.glusterfs/c1/ca/ directory. > >Now I manually set the trusted.gfid value on the file, and launched >heal again, >and now gluster was able to heal it OK! Healing is now fully complete, >and no out-of-sync files anymore. > >Any idea what caused the missing trusted.gfid ? > >Do you want to raise a bug for this? We would love to if you don't have >the time to make sure we address this. > Sure. Should I file the bug on redhat bugzilla? -- Pasi ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] gluster 3.7 healing errors (no data available, buf->ia_gfid is null)
On Thu, Sep 22, 2016 at 09:58:25AM +0530, Ravishankar N wrote: > On 09/21/2016 10:54 PM, Pasi Kärkkäinen wrote: > >Let's see. > > > ># getfattr -m . -d -e hex /bricks/vol1/brick1/foo > >getfattr: Removing leading '/' from absolute path names > ># file: bricks/vol1/brick1/foo > >security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000 > > > >So hmm.. no trusted.gfid it seems.. is that perhaps because this node was > >down when the file was created? > > No, even if that were the case, the gfid should have been set while > healing the file to this node. > Can you try doing a setfattr -n trusted.gfid -v > 0xc1ca778ed2af4828b981171c0c5bd45e on the file. and launch heal > again? > What about the .glusterfs hardlink- does that exist? > It seems there's no hardlink.. nothing in /bricks/vol1/brick1/.glusterfs/c1/ca/ directory. Now I manually set the trusted.gfid value on the file, and launched heal again, and now gluster was able to heal it OK! Healing is now fully complete, and no out-of-sync files anymore. Any idea what caused the missing trusted.gfid ? Thanks a lot! -- Pasi ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] gluster 3.7 healing errors (no data available, buf->ia_gfid is null)
Hi, On Wed, Sep 21, 2016 at 10:12:44PM +0530, Ravishankar N wrote: > On 09/21/2016 06:45 PM, Pasi Kärkkäinen wrote: > >Hello, > > > >I have a pretty basic two-node gluster 3.7 setup, with a volume > >replicated/mirrored to both servers. > > > >One of the servers was down for hardware maintenance, and later when it got > >back up, the healing process started, re-syncing files. > >In the beginning there was some 200 files that need to be synced, and now > >the number of files is down to 10, but it seems the last 10 files don't seem > >to get synced.. > > > >So the problem is the healing/re-sync never ends for these files.. > > > > > ># gluster volume heal gvol1 info > >Brick gnode1:/bricks/vol1/brick1 > >/foo > >/ - Possibly undergoing heal > > > >/foo6 > >/foo8 > >/foo7 > >/foo9 > >/foo2 > >/foo5 > >/foo4 > >/foo3 > >Status: Connected > >Number of entries: 10 > > > >Brick gnode2:/bricks/vol1/brick1 > >/ > >Status: Connected > >Number of entries: 1 > > > > > >In the brick logs for the volume I see these errors repeating: > > > >[2016-09-21 12:41:43.063209] E [MSGID: 113002] [posix.c:252:posix_lookup] > >0-gvol1-posix: buf->ia_gfid is null for /bricks/vol1/brick1/foo [No data > >available] > >[2016-09-21 12:41:43.063266] E [MSGID: 115050] > >[server-rpc-fops.c:179:server_lookup_cbk] 0-gvol1-server: 1484202: LOOKUP > >/foo (----0001/foo) ==> (No data available) [No > >data available] > > > > > >Any idea what might cause those errors? (/foo is exactly the file that is > >being healed, but fails to heal) > >Any tricks to try? > > Can you check if the 'trusted.gfid' xattr is present for those files > on the bricks and the files also have the associated hardlink inside > .glusterfs? You can refer to > https://joejulian.name/blog/what-is-this-new-glusterfs-directory-in-33/ > if you are not familiar with the .glusterfs directory. > Let's see. # getfattr -m . -d -e hex /bricks/vol1/brick1/foo getfattr: Removing leading '/' from absolute path names # file: bricks/vol1/brick1/foo security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000 So hmm.. no trusted.gfid it seems.. is that perhaps because this node was down when the file was created? On another node: # getfattr -m . -d -e hex /bricks/vol1/brick1/foo getfattr: Removing leading '/' from absolute path names # file: bricks/vol1/brick1/foo security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.afr.dirty=0x trusted.afr.gvol1-client-1=0x16620001 trusted.bit-rot.version=0x020057e00db5000624ed trusted.gfid=0xc1ca778ed2af4828b981171c0c5bd45e So there we have the gfid.. How do I fix this and allow healing process to continue/finish.. ? Thanks, -- Pasi > -Ravi > > > > >Software versions: CentOS 7 with gluster37 repo (running Gluster 3.7.15), > >and nfs-ganesha 2.3.3. > > > > > >Thanks a lot, > > > >-- Pasi > > ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] gluster 3.7 healing errors (no data available, buf->ia_gfid is null)
Hello, I have a pretty basic two-node gluster 3.7 setup, with a volume replicated/mirrored to both servers. One of the servers was down for hardware maintenance, and later when it got back up, the healing process started, re-syncing files. In the beginning there was some 200 files that need to be synced, and now the number of files is down to 10, but it seems the last 10 files don't seem to get synced.. So the problem is the healing/re-sync never ends for these files.. # gluster volume heal gvol1 info Brick gnode1:/bricks/vol1/brick1 /foo / - Possibly undergoing heal /foo6 /foo8 /foo7 /foo9 /foo2 /foo5 /foo4 /foo3 Status: Connected Number of entries: 10 Brick gnode2:/bricks/vol1/brick1 / Status: Connected Number of entries: 1 In the brick logs for the volume I see these errors repeating: [2016-09-21 12:41:43.063209] E [MSGID: 113002] [posix.c:252:posix_lookup] 0-gvol1-posix: buf->ia_gfid is null for /bricks/vol1/brick1/foo [No data available] [2016-09-21 12:41:43.063266] E [MSGID: 115050] [server-rpc-fops.c:179:server_lookup_cbk] 0-gvol1-server: 1484202: LOOKUP /foo (----0001/foo) ==> (No data available) [No data available] Any idea what might cause those errors? (/foo is exactly the file that is being healed, but fails to heal) Any tricks to try? Software versions: CentOS 7 with gluster37 repo (running Gluster 3.7.15), and nfs-ganesha 2.3.3. Thanks a lot, -- Pasi ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
