Re: [Gluster-users] Online upgrade - 9.x to 10.0
Am Di., 28. Dez. 2021 um 23:10 Uhr schrieb Marco Fais : > Hi Michael > > unfortunately not -- everything I tried brings me to the same situation > where the peer is rejected. > I have also replicated the issue in another cluster where I can experiment > without issues, but not sure what I should try next... > > Regards, > Marco > Hey Marco, probably just wait. Nikhil responded to my other mail on the list - he's pretty sure it is about the checksum mismatch caused by a removed deprecated option in the info file: https://lists.gluster.org/pipermail/gluster-users/2021-December/039733.html There is also a link to the corresponding github issue. If the fix is gonna make it into 10.1 you could try again. The earliest my schedule will allow me this will be likely in 2-3 months. Regards Mika 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] Unable to upgrade nodes because of cksums mismatch
Am Mo., 27. Dez. 2021 um 16:25 Uhr schrieb Nikhil Ladha : > > On Mon, Dec 27, 2021 at 7:24 PM Michael Böhm > wrote: > >> Am Mo., 27. Dez. 2021 um 14:04 Uhr schrieb Nikhil Ladha < >> nla...@redhat.com>: >> >>> Hi Michael >>> >>> I think you are hitting a similar issue like this one >>> https://github.com/gluster/glusterfs/issues/3066. >>> If so, the fix for the same is under review and could be available in >>> the next release. >>> >> >> Thanks for your reply. I saw that issue and thought it doesn't really >> apply to me cause i don't use striping (only Replicate and one >> Distributed-Replicate). But maybe, if this is a cause for the mismatched >> cksum, it could be the root cause >> > > Yes, the missing stripe count from the volfile after the upgrade is > causing the checksum mismatch and hence the "peer-rejected" issue. > Aah i see - i subscribed to the issue to keep track when this is potentially resolved. > > >> I always hesitate to upgrade to a x.0 version - but as those holidays are >> the best time for these upgrades i thought i might skip v9 this time. >> >> To close this for me, as i have a lot of updates to do and this was one of the prequisites, i downgraded the host to v9.4 and this didn't cause any errors. I will now upgrade all other nodes to 9.4. As the release schedule changed with v10 and the world we live in atm is generally slowing everything down i hope to stay on a maintained v9 until late next year - and that's totally fine with me. 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] Unable to upgrade nodes because of cksums mismatch
Am Mo., 27. Dez. 2021 um 14:04 Uhr schrieb Nikhil Ladha : > Hi Michael > > I think you are hitting a similar issue like this one > https://github.com/gluster/glusterfs/issues/3066. > If so, the fix for the same is under review and could be available in the > next release. > Thanks for your reply. I saw that issue and thought it doesn't really apply to me cause i don't use striping (only Replicate and one Distributed-Replicate). But maybe, if this is a cause for the mismatched cksum, it could be the root cause. I always hesitate to upgrade to a x.0 version - but as those holidays are the best time for these upgrades i thought i might skip v9 this time. 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] Online upgrade - 9.x to 10.0
Hey Marco, >> On Fri, Nov 19, 2021 at 4:07 AM Marco Fais wrote: >> >>> Hi all, >>> >>> is the online upgrade from 9.x to 10.0 supported? >>> >>> ... > >>> Trying to restart the upgraded glusterd node doesn't help. I have also >>> tried to clean up /var/lib/glusterd without success. >>> >>> Am I missing something? >>> >>> Downgrading again to 9.3 works again. All my volumes are >>> distributrd_replicate and the cluster is composed by 3 nodes. >>> >>> Did you ever resolve this issue? I am at the exact same point and see the downgrade as the only option, but i have a few days left to test around with this issue. Regards Mika > 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] GlusterFS 9 and Debian 11
Am Mi., 29. Sept. 2021 um 14:17 Uhr schrieb Taste-Of-IT < kont...@taste-of-it.de>: > Hi, > i looked again on the source share and the correct and working sources are: > > echo deb [arch=amd64] > https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/bullseye/amd64/apt > bullseye main > /etc/apt/sources.list.d/gluster.list > > Now its working - sorry for my mistake, but thanks for your fast helping .. > [closed] > np - and yes that line is also correct if you want to stay on the latest 9 release for bullseye. 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] GlusterFS 9 and Debian 11
Am Mi., 29. Sept. 2021 um 13:10 Uhr schrieb Taste-Of-IT < kont...@taste-of-it.de>: > Hi, > server: > > # apt policy glusterfs-server > glusterfs-server: > Installiert: (keine) > Installationskandidat: 9.3-1 > Versionstabelle: > 9.3-1 500 > 500 > https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/buster/amd64/apt > buster/main amd64 Packages > 9.2-1 500 > 500 http://deb.debian.org/debian bullseye/main amd64 Packages > > Client: > # apt policy glusterfs-client > glusterfs-client: > Installiert: (keine) > Installationskandidat: 9.3-1 > Versionstabelle: > 9.3-1 500 > 500 > https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/buster/amd64/apt > buster/main amd64 Packages > 9.2-1 500 > 500 http://deb.debian.org/debian bullseye/main amd64 Packages > Looks like the sources for buster - sources list should be: # GlusterFS Apt Repository deb https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/11/amd64/apt bullseye main 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] GlusterFS 9 and Debian 11
Am Mi., 29. Sept. 2021 um 11:43 Uhr schrieb Taste-Of-IT < kont...@taste-of-it.de>: > Hi, > > i tested it again: i installed debian 11 from debian dvd1, i added sources > for glusterfs 9.3-1. After updating the system and sources i got the same > error message. > what's the output of "apt policy glusterfs-server" / "apt policy glusterfs-client" 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] GlusterFS 9 and Debian 11
Am Mi., 22. Sept. 2021 um 13:51 Uhr schrieb Taste-Of-IT < kont...@taste-of-it.de>: > Hi, > > i installed fresh Debian 11 stable and use GlusterFS latest sources. At > installing glusterfs-server i got error missing libreadline7 Paket, which > is not in Debian 11. > > Hey, what is the exact repo you used? Looking at the Packages-file [1] - the glusterfs-server version from the bullseye repo of glusterfs should depend on "libreadline8 (>= 6.0)" [1] https://download.gluster.org/pub/gluster/glusterfs/9/LATEST/Debian/bullseye/amd64/apt/dists/bullseye/main/binary-amd64/Packages 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] Upgrade from 4.1
Am Mo., 9. März 2020 um 22:34 Uhr schrieb Marcus Pedersén < marcus.peder...@slu.se>: > Hi all, > Hey Marcus I just want to double check before I start my upgrade of gluster. > I am running 4.1 (distributed, replicated) today and I want to upgrade > to version 7. > What I understand from the documentation there is no need to upgrade > to a intermediate version before I upgrade to version 7. > I can directly upgrade 4.1 -> 7, am I correct? > Yes that's correct, earliest version you could directly upgrade from is 3.12. That's what i had to do and it all went well. > Second question, is there a problem running an older version of gluster > on the client side? > If servers are version 7 and clients have version 5 or 6, is this a > problem? > Well i wouldn't recommend in the long term. After the upgrade it is advised to bump the op-version[1] and that could be a problem with the old clients. But as i don't know the supported feature-sets i leave that question to the experts here ;-) > Best regards > Marcus > Good Luck Mika [1] https://docs.gluster.org/en/latest/Upgrade-Guide/op_version/ Community Meeting Calendar: Schedule - Every 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] recommendation: gluster version upgrade and/or OS dist-upgrade
Am Do., 20. Feb. 2020 um 13:48 Uhr schrieb Hu Bert : > Hi Mika, > > i did a test on my 5.x test cluster. I started with the dist-upgrade > stretch -> buster, which went fine. But "updating" from the glusterfs > packages stretch -> buster was not possible, i had to deinstall the > stretch packages and reinstall the buster packages. > Aah sorry i misread your mail, i thought you upgraded all the way from gluster 3.x. So you used the glusterfs-repo the whole time. Well for the dist-upgrade it is always recommended to disable external repositories. And then i wouldn't try to go directly from a stretch-"5"-package to buster-"6" - instead: either: stretch-"5" -> stretch-"6" -> buster-"6" or: stretch "5" -> buster-"5" -> buster-"6" I don't think removing and reinstalling the packages should be necessary, but as long as it worked for you all is good.. Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] recommendation: gluster version upgrade and/or OS dist-upgrade
Am Di., 18. Feb. 2020 um 08:51 Uhr schrieb Hu Bert : > Hello, > > i currently have a replicate 3 setup, gluster version 5.11 and debian > stretch. In the next weeks i want to migrate to gluster version 6.x > and upgrade the OS to debian buster. > > So... any recommendation of what to do first? First upgrade gluster or > the operating system? > Hello Hubert, i needed to do this a while ago, in my case it was a Proxmox-Cluster based on the Debian Stretch upgrade to Buster while also upgrading gluster up to v7. The way i did it: 1. i had the "normal" stretch gluster packages installed (3.8) not the backports (4.1), so i first needed to upgrade gluster to 3.12 and move on from there (see [1]). You may be able to skip the next step. 2. i activated the old-releases gluster repos for 3.12 [2] and upgrade from 3.8(debian) to 3.12(gluster) 3. after this i switched to the "latest" repo and upgraded to v7 while still running stretch 4. then i upgraded stretch to buster, while gluster repos where commented out 5. after the dist-upgrade i switched the gluster repos to the buster ones and activated them again I write this all from memory as i am not at work atm, but this should be it. I also can say, that i did all the upgrades online (couldn't afford to stop all the vm's) - and to my surprise everything went without a big problem. Good luck Mika [1] https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_7/ or https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_6/ [2] https://download.gluster.org/pub/gluster/glusterfs/old-releases/3.12/LATEST/Debian/9/ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Debian Repository changed urls
Hello, according to [1] i am using the following url for the apt-repo: > deb https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/10/amd64/apt buster main I know the 7.2 is not ready there yet, that's not the problem. But since last Saturday (18.01.20) my servers can't find a Release file there. I've browsed manually and it seems i have to use: > deb https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/buster/amd64/apt buster main now - is that right? Regards Mika [1] https://docs.gluster.org/en/latest/Install-Guide/Install/ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] healing of big files
Am Di., 14. Jan. 2020 um 10:38 Uhr schrieb vlad f halilov :
> Hi there. I'm trying to deploy replicated 2+1 cluster with gluster 5.5.1
> (debian 10) as vm image storage for libvirt, but have an issue with
> healing disconnected node. Example:
>
...
>
> 4) After node5 has reconnected, healing procedure has begun, but looks
> that about to entire file have transferred from synced node to unsynced,
> instead just changed blocks. (ifconfig on node5 showed 'RX
> packets 269790 bytes 5293724127 (4.9 GiB)) - so little less than 5Gb
> file' I tried 'difff' mode (gluster volume set vmpool
> cluster.data-self-heal-algorithm diff) but with no effect. Any idea,
> whats wrong?
>
Actually i think diff should be working the way you expect it to, but diff
is very cpu-intensive as it needs to calculate and check checksums.
I would advise you to look at the example configuration for volumes with
vm-disks, it should be "/var/lib/glusterd/groups/virt". The main thing is
sharding is activated ("split big files internally in many small ones") and
set heal-algorithm to full.
This way heal is very fast, as it only resyncs the changed shards without
the need of checksums. I use it the same way on multiple hosts, each with
about 20-30 vms.
And Check the value of "features.shard-block-size", don't know what the
default is atm - i use 64MB and it works quite well.
Regards.
Mika
Community Meeting Calendar:
APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/441850968
NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/441850968
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] periodical warnings in brick-log after upgrading to gluster 7.1
Am Di., 31. Dez. 2019 um 06:52 Uhr schrieb Amar Tumballi : > > I noticed that this is happening when a client disconnects with server > (specially, after umount). Was there any periodic umount which is > happening? Or a monitoring system which is running, which would do a > temporary mount and and check for size etc ? > Aah yeah of course, something outside must trigger it. Well the mounts are handled by proxmox and nagios does regular heal-checks - so already two things i can check when i get back to work. > Regards, > Amar > Thank you Mika Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT 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 Gluster release 7.1
Yes they are - they appeared like an hour later. I thought that was you. I already updated all of our servers shortly afterwards. Thanks anyway Am Mo., 30. Dez. 2019 um 14:38 Uhr schrieb Rinku Kothiya < rkoth...@redhat.com>: > Hi Michael, > > The Debian packages, are already available via the LATEST-repo? > > Regards > Rinku > > On Fri, Dec 27, 2019 at 3:59 PM Michael Böhm > wrote: > >> Hello Rinku, >> >> thanks for the Debian packages, do you know when they will be available >> via the LATEST-repo? >> >> https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/ >> >> Regards >> >> Mika >> >> >> Am Fr., 27. Dez. 2019 um 08:39 Uhr schrieb Rinku Kothiya < >> rkoth...@redhat.com>: >> >>> Hi, >>> >>> Debian packages are also available now for Gluster7.1. >>> >>> Thanks, >>> Gluster community >>> >>> *References:* >>> >>> *[1] Packages for 7.1:* >>> https://download.gluster.org/pub/gluster/glusterfs/7/7.1/ >>> >>> *[2] Release notes for 7.1:* >>> https://docs.gluster.org/en/latest/release-notes/7.1/ >>> >>> On Tue, Dec 24, 2019 at 11:21 PM Rinku Kothiya >>> wrote: >>> >>>> Hi, >>>> >>>> The Gluster community is pleased to announce the release of Gluster7.1 >>>> (*packages >>>> available at [1]*). >>>> Release notes for the release can be found at* [2]*. >>>> >>>> Major changes, features and limitations addressed in this release: >>>> None >>>> >>>> *Apologies for the missing debian packages, we are working on it and >>>> will release it soon. * >>>> >>>> Thanks, >>>> Gluster community >>>> >>>> *References:* >>>> >>>> *[1] Packages for 7.1:* >>>> https://download.gluster.org/pub/gluster/glusterfs/7/7.1/ >>>> >>>> *[2] Release notes for 7.1:* >>>> https://docs.gluster.org/en/latest/release-notes/7.1/ >>>> >>> >>> >>> Community Meeting Calendar: >>> >>> APAC Schedule - >>> Every 2nd and 4th Tuesday at 11:30 AM IST >>> Bridge: https://bluejeans.com/441850968 >>> >>> NA/EMEA Schedule - >>> Every 1st and 3rd Tuesday at 01:00 PM EDT >>> Bridge: https://bluejeans.com/441850968 >>> >>> Gluster-users mailing list >>> Gluster-users@gluster.org >>> https://lists.gluster.org/mailman/listinfo/gluster-users >>> >> >> >> Community Meeting Calendar: >> >> APAC Schedule - >> Every 2nd and 4th Tuesday at 11:30 AM IST >> Bridge: https://bluejeans.com/441850968 >> >> NA/EMEA Schedule - >> Every 1st and 3rd Tuesday at 01:00 PM EDT >> Bridge: https://bluejeans.com/441850968 >> >> Gluster-users mailing list >> Gluster-users@gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users >> > Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] periodical warnings in brick-log after upgrading to gluster 7.1
Hello, i've finally upgraded our gluster-server to 7.1 (3.8 debian stretch -> gluster-repo 3.12 -> gluster-repo 7.1) and it actually went real smooth. There is just that warning in all brick-logs and every server every 15min i can't really explain myself. [2019-12-29 05:51:17.807293] W [socket.c:774:__socket_rwv] 0-tcp.store4-server: readv on 192.168.31.60:49077 failed (no data available) [2019-12-29 06:00:47.886369] W [socket.c:774:__socket_rwv] 0-tcp.store4-server: readv on 192.168.31.61:49140 failed (no data available) [2019-12-29 06:06:18.204778] W [socket.c:774:__socket_rwv] 0-tcp.store4-server: readv on 192.168.31.60:49077 failed (no data available) [2019-12-29 06:15:47.317705] W [socket.c:774:__socket_rwv] 0-tcp.store4-server: readv on 192.168.31.61:49148 failed (no data available) .60 and .61 are two servers with bricks for gluster volume "store4". They are not only the gluster-server, they also are clients that mount the gluster volumes. (replicated gluster volume, that hosts kvm images that run locally on the server) Everything really looks good no other errors or warning - just the lines mentioned above. Is this something i should be worried about or can resolve somehow? Of course i looked through the web, unfortunately i only really could find one guy that had the same problem but no following messages [1]. And the best explanation i could find was in a bug report [2], so it seems it's not unusual i just don't like ignoring warnings. Anyone here that has similiar warning or could explain what i can do about it? Thanks Mika [1] https://lists.gluster.org/pipermail/gluster-users/2015-May/021971.html [2] https://bugzilla.redhat.com/show_bug.cgi?id=1385525#c3 Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT 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 Gluster release 7.1
Hello Rinku, thanks for the Debian packages, do you know when they will be available via the LATEST-repo? https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/ Regards Mika Am Fr., 27. Dez. 2019 um 08:39 Uhr schrieb Rinku Kothiya < rkoth...@redhat.com>: > Hi, > > Debian packages are also available now for Gluster7.1. > > Thanks, > Gluster community > > *References:* > > *[1] Packages for 7.1:* > https://download.gluster.org/pub/gluster/glusterfs/7/7.1/ > > *[2] Release notes for 7.1:* > https://docs.gluster.org/en/latest/release-notes/7.1/ > > On Tue, Dec 24, 2019 at 11:21 PM Rinku Kothiya > wrote: > >> Hi, >> >> The Gluster community is pleased to announce the release of Gluster7.1 >> (*packages >> available at [1]*). >> Release notes for the release can be found at* [2]*. >> >> Major changes, features and limitations addressed in this release: >> None >> >> *Apologies for the missing debian packages, we are working on it and will >> release it soon. * >> >> Thanks, >> Gluster community >> >> *References:* >> >> *[1] Packages for 7.1:* >> https://download.gluster.org/pub/gluster/glusterfs/7/7.1/ >> >> *[2] Release notes for 7.1:* >> https://docs.gluster.org/en/latest/release-notes/7.1/ >> > > > Community Meeting Calendar: > > APAC Schedule - > Every 2nd and 4th Tuesday at 11:30 AM IST > Bridge: https://bluejeans.com/441850968 > > NA/EMEA Schedule - > Every 1st and 3rd Tuesday at 01:00 PM EDT > Bridge: https://bluejeans.com/441850968 > > Gluster-users mailing list > Gluster-users@gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users > Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Switching from Debian Packages to Gluster Community Packages
Hey folks, Question ist essentially in the Subject. Right now i'm running Debian oldstable/stretch with Gluster 3.8.8 from the normal repo and i'm thinking about switching to the community repo from gluster. I couldn't find much about which problems i can expect. I checked the packages, and besides that the debian packages still have init-scripts and the ones from gluster are already systemd offering only the unit file. In the end i would like to get from gluster 3 -> 6 in as few steps as possible, if i stay in with the debian packages that would mean: 3.8.8 (stretch) -> 4.1 (stretch-backports) -> 5.5 (buster) -> 6.4 (buster-backports) If i can use the gluster-repos that would be only: 3.8.8 (stretch) -> 3.12 (gluster-repo) -> 6.5 (gluster-repo) Will this be possible? And of course i want to do that online, i have only replicate and distributed-replicate volumes. Regards Mika ___ Gluster-users mailing list Gluster-users@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users
