bryancall commented on PR #12609: URL: https://github.com/apache/trafficserver/pull/12609#issuecomment-3874080339
**Feature comparison: storage.config + volume.config vs storage.yaml** I compared the documented features in the existing config files against the new `storage.yaml` docs and found a few gaps: | # | Missing from storage.yaml docs | Notes | |---|-------------------------------|-------| | 1 | **Human-readable size suffixes** (K, M, G, T) | `storage.config` documents these. The new YAML examples only show raw byte values (e.g., `134217728` instead of `128M`). Should document whether YAML sizes support the same suffixes. | | 2 | **Fragment size maximum** (4MB) | `volume.config` documents "this setting has a maximum value of 4MB". Not mentioned in `storage.yaml` `fragment_size` description. | | 3 | **Cache invalidation warning** | Both `storage.config` and `volume.config` warn that changes effectively invalidate the cache. The new `storage.yaml` docs do not include this warning. | | 4 | **Minimum span/volume sizes** | `storage.config` says "a formatted or raw disk must be at least 128 MB". `volume.config` says "128 MB is the smallest value" and sizes must be multiples of 128 MB. Not mentioned in `storage.yaml`. | | 5 | **Striping behavior** | `volume.config` explains how volumes stripe across disks for parallel I/O. This is useful context missing from the new docs. | Items 1-3 are the most important -- users will hit these in practice. 4 and 5 are nice-to-have. Otherwise the docs look thorough. The examples are clear, the backwards compatibility section is helpful, and the `avg_obj_size` / `fragment_size` per-volume overrides are well documented. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
