You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Daschinsky (Jira)" <ji...@apache.org> on 2021/05/28 11:24:00 UTC
[jira] [Updated] (IGNITE-14796) Support of deallocating file space
not checked during initialization of CacheCompressionManager
[ https://issues.apache.org/jira/browse/IGNITE-14796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Daschinsky updated IGNITE-14796:
-------------------------------------
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required)
> Support of deallocating file space not checked during initialization of CacheCompressionManager
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-14796
> URL: https://issues.apache.org/jira/browse/IGNITE-14796
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.10
> Reporter: Ivan Daschinsky
> Priority: Major
> Labels: compression
>
> Support of deallocating file space currently is not checked during initialization of CacheCompressionManager.
> According to [man page|https://man7.org/linux/man-pages/man2/fallocate.2.html],
> {{fallocate}} supports "punching hole" only on small subset of filesystems. We should check it during initialization of CacheCompressionManager.
> By the way in the method {{org.apache.ignite.internal.processors.compress.NativeFileSystemLinux#punchHole}} {{errno}} incorrectly processed. {{fallocate}} on error returns always {{-1}} and set {{errno}}. Currently this method returns only {{-1}} that misleads user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)