Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: officially stop supporting 32-bit platforms beginning with 7.0 #702

Closed
kalebskeithley opened this issue Aug 1, 2019 · 9 comments
Closed
Labels
platform Any platform specific questions/issues can be tagged with this label Type:ReleaseActivity wontfix Managed by stale[bot]

Comments

@kalebskeithley
Copy link
Contributor

Not really an enhancement.

I suggested this somewhere, IRC, -dev mailing list, not sure. Nor am I sure that it registered.

I seriously doubt anyone is running on 32-bit platforms any more. Even Raspberry-Pi is 64-bit now. Even Ceph has stopped supporting 32-bit with Nautilus/14.x.x.

But it's probably still worth continuing to build it on 32-bit in the CI just to keep people honest (and correct) about sprintf format strings and other 32-bit-isms.

@amarts
Copy link
Member

amarts commented Aug 5, 2019

I am happy with this proposal, and we can do this from glusterfs-8 (another 3-4 months).

Let the smoke run, so we can capture any formatting errors etc.

@mykaul
Copy link
Contributor

mykaul commented Aug 5, 2019

Would be nice to move to all native int (64b) in the return codes (and align with ssize_t where it makes sense - system calls such as lgetxattr for example)

@jameshilliard
Copy link

Even Raspberry-Pi is 64-bit now.

Newer versions are but I expect older versions would still be used for a while.

@amarts amarts added platform Any platform specific questions/issues can be tagged with this label Type:ReleaseActivity labels Oct 17, 2019
@amarts
Copy link
Member

amarts commented Oct 17, 2019

Now that glusterfs-7.0 is almost ready, should we take this proposal and agree to go ahead?

The change is only in having a officially available build of 32bit, and code will still continue to work on 32bit (as we will have smoke test for the same).

@stale
Copy link

stale bot commented May 14, 2020

Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.

@stale stale bot added the wontfix Managed by stale[bot] label May 14, 2020
@stale
Copy link

stale bot commented May 29, 2020

Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it.

@stale stale bot closed this as completed May 29, 2020
@JonChesterfield
Copy link

JonChesterfield commented Aug 31, 2020

What was the resolution to this? The two platforms I would most like to run glusterfs on are the odroid hc2 (arm) and the pc engines apu2 (x86), both of which 32 bit, but I'll keep looking for a 64 bit alternative if necessary.

edit: actually misread the spec on jaguar, the apu2 is x86-64. So it's only the hc2 that is still of interest to me.

@PhilippKuntschik
Copy link

sorry for the bump.

@JonChesterfield I have the same issue: 4 odroid xu4 boards that only run 32bit. May I ask if you have a solution to host a distributed file system on these machines? Or did you go forward to replace the boards all together?

@k-van-man
Copy link

The Odroid HC1 is also 32 bit, and now running Ubuntu 22.04 with k3s up-and-running, For the fun part I want to install GlusterFS that works, but it will not run, it crashes with a coredump. Isn't there a small fix? Or can I use another 32-bit supported version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform Any platform specific questions/issues can be tagged with this label Type:ReleaseActivity wontfix Managed by stale[bot]
Projects
None yet
Development

No branches or pull requests

7 participants