-
Notifications
You must be signed in to change notification settings - Fork 55
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
segment_above verification failed on rpi #120
Comments
I think that all other calculations return a wrong value. I'm limited to 2Mb filesize. I get an operation not permitted error.
|
I'm not sure to see the issue.
Is really 5Gb. On the RasP what the size for an unsigned long? |
Using the following program on a Raspberry Pi
I get the output:
So it appears the size is 32-bit, limited to 4294967296, and it can't hold the value of 5 billion. |
So that's a 32bit Raspberry Pi, and files above 4Gb cannot be supported. |
Is it not possible to switch to the "unsigned long long" type? |
Is that supported on Raspberry Pi? And this is probably not supported on all 64bit machines. Not easy. |
Unsigned long long has the same 8 byte size both on 32-bit and on 64-bit machines.
Result on Raspberry Pi:
Result on AMD FX-8350 (amd64):
As you can see the size of unsigned long differs, but unsigned long long stays the same across both platforms. |
Note that current version of hubicfuse should already handle this properly. On 32bit system the segment is max 2Gb. Look at new code, it seems you have an old version. Can you double check with current sources? |
Hi,
Similar to #64, size calculation is wrong on a Raspberry Pi B+. FiveGb size is 1073741824.
Debug source code :
Result :
Why don't you set 5368709120 value to FiveGb ?
Best regards.
The text was updated successfully, but these errors were encountered: