-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
openZFS 2.0 rc3 reports fallocate supported, but not works #11073
Comments
@wheelcomplex thanks for opening this issue. The ZFS behavior you're seeing is what was intended. Partial support for
This is functionally correct and achieves what callers are really after while avoiding the expense of preallocating blocks which won't be used. There's a good discussion in issue #326 covering the various tradeoffs and concerns. If possible I'd suggest updating the test case to not worry about the internal filesystem details of exactly how many blocks were actually allocated. |
Thanks for the explaining and suggestion. |
Basic fallocate(mode=0/2) compatibility has been added in openZFS 2.0. Test case TestFallocate has been suggested to skip on ZFS (openzfs/zfs#11073). fix: golang#42005 Change-Id: Ic7ea6cbcb076c8e422c4136950b5e1f2c034955c
Basic fallocate(mode=0/2) compatibility has been added in openZFS 2.0. Test case TestFallocate has been suggested to skip on ZFS (openzfs/zfs#11073). fix: golang#42005 Change-Id: Ic7ea6cbcb076c8e422c4136950b5e1f2c034955c
Read this Go issuse for reference.
System information
Distribution Name | Ubuntu
Distribution Version | 20.04
Linux Kernel | 5.4.0-48-generic
Architecture | x86_64
ZFS Version | 2.0.0-rc3
SPL Version | 2.0.0-rc3
Describe the problem you're observing
openZFS 2.0 rc3 reports fallocate supported, but not works
Describe how to reproduce the problem
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: