# cephfs Published articles for cephfs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Reclaim Ceph Capacity Through CephFS Transcoding DevFeed: [Reclaim Ceph Capacity Through CephFS Transcoding]() Original publisher: [Read original article]() Author: Anthony D'Atri Published: 2026-07-01T00:00:00Z Content type: article Language: en Sources: [Ceph Blog]() Topics: [Transcodings](), [Software](), [data]() Tags: [2026](), [4k](), [article](), [blog-post](), [ceph](), [cephfs](), [dram](), [efficiency](), [en-article](), [en-blog-post](), [enterprise](), [enterprise-storage](), [filesystem](), [fujitsu](), [git](), [hardware](), [performance](), [software](), [space](), [storage](), [tentacle]() ### AI overview This article addresses rising storage demands and hardware costs by discussing CephFS capacity efficiency. It describes replicated pools, Erasure Coding, and Fast EC in Ceph Tentacle, while the title identifies CephFS transcoding as the article's focus. ### Source excerpt Data expands to fill available storage (and beyond)! ¶ It used to be that enterprise storage meant 6RU rackmount Fujitsu 2351 Eagles, each holding a mind-boggling 380 MiB of data: enough for a whole company! Today that 380 MiB can't even hold a 4k pickleball video. Enterprises, educational instutitions, and really just about anyone these days demand storage capacities that start on the order of hundreds of tebibytes and rapidly grow to pebibytes. As this article is written in the spring of 2026, the memory market, which includes DRAM, SSDs, and legacy HDDs, has experienced a dramatic escalation of pricing. It is not uncommon to be quoted a price four times what the same hardware cost a year ago, and there are signs that it is going to get worse before it gets better. What's a poor ammonite to do?? Cephers find themselves between the Charybdis of quotes approaching Disaster Area's hypermathematics and the Scylla of hungry users armed with torches and git forks. Git forks, pitchforks. Get it? Sigh. Tough room. Anyway... Short of nuking the site from orbit, how do we make everyone happy, or at worst mildly discontented? Efficiency! CephFS ¶ CephFS is a popular, highly available and scalable software-defined POSIX-style distributed filesystem that can easily store tens of pebibytes of precious data. Or, alternately, cat videos. Ceph deployments often begin small, with replicated pools for perceived performance needs. As the cluster grows to more nodes and more data, it may become feasible and desirable to switch to Erasure Coding (EC) to make more efficient use of raw capacity. An EC pool thus can require substantially less raw storage for a given amount of user data, or store gobs more user data on a given amount of raw capacity This EC overhead table presents efficiency (space amplification) factors for a spectrum of EC profiles. Replicated pools usually maintain three copies of data, so for comparison they manifest an overhead factor of 3.0. EC 4+2 or 6+3 presents a ## v19.2.4 Squid released DevFeed: [v19.2.4 Squid released]() Original publisher: [Read original article]() Author: Yuri Weinstein Published: 2026-06-01T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [cephfs](), [Kafka](), [dashboards](), [Authorization](), [Tooling]() Tags: [blog-post](), [bug](), [cephfs](), [en-article](), [en-blog-post](), [json](), [kafka](), [release](), [squid](), [update]() ### AI overview Ceph v19.2.4 Squid is the fourth backport release in the Squid series, and the article recommends that all users update. Changes include BlueFS storage adjustments, fixes in RADOS and RADOS Gateway, Kafka 3.9.2 support, CephFS and MDS diagnostic and consistency improvements, Dashboard service and access-control fixes, and an RBD lock policy change. ### Source excerpt This is the fourth backport release in the Squid series. We recommend all users update to this release. Notable Changes ¶ OSD / BlueStore ¶ BlueFS: Increased the default WAL volume size to 1GB to prevent ENOSPC failures. Volume Selection: Fixed the usage of bluestore_volume_selection_reserved_factor and updated row naming conventions in RocksDBBlueFSVolumeSelector. Health: Added a time_added field to mon_info_t to prevent freshly added monitors from incorrectly triggering a MON_DOWN health status. Tooling: Updated monmaptool to correctly respect set features when adding addresses. RADOS / Manager (mgr) ¶ RADOS pybind: Fixed a parameter reversal bug in WriteOp.zero() where offset and length were swapped when calling the underlying C API. Daemon Health: Modified the manager to clear health metrics for down or out OSDs instead of removing them entirely from the daemon state. Autoscaler: Updated pg_autoscale_mode logic to accurately reflect the no_autoscale flag in both standard and JSON command outputs. RADOS Gateway (RGW) ¶ Notifications: Resolved a reserved_size drift in the 2pc_queue causing ENOSPC errors and fixed a leak where overhead was not properly decremented during commit/abort. Multipart Uploads: Fixed an issue where tags could not be retrieved from objects created via multipart uploads. Kafka Integration: Updated the internal Kafka version support to 3.9.2. CephFS / MDS ¶ Fragments: Simplified fragment printing and corrected frag_t endianness conversion for network and storage consistency. FUSE Client: Updated the FUSE client to clarify that fallocate disk space reservation is only supported with specific flags like FALLOC_FL_KEEP_SIZE. Metadata: Updated the MDS to dump frag_t as an object and included sysinfo in the status command output for better diagnostics. Dashboard ¶ Services: Fixed a bug where changing MDS placement to a label incorrectly triggered the creation of an entirely new MDS service. Access Control: Fixed role-based access control permissio