mirror of https://github.com/rustfs/rustfs.git synced 2026-08-05 12:57:42 +00:00

Files

T

houseme 6f05a740b3 refactor(ecstore): extract the shared io_uring read preamble (backlog#1145) (#4696 )

`pread_uring` and `pread_uring_direct` accumulated across seven rounds
(#4632/#4635/#4645/#4649/#4653/#4658/#4662) and each carried its own copy of
the same open preamble: resolve the bucket path, run the volume access check,
resolve the object path, and check the path length. The only real difference
is what happens after — one opens buffered and errors as `DiskError`, the
other opens `O_DIRECT` and errors as `DirectOpenError` so it can latch an
O_DIRECT refusal.

Extract that shared sequence into `resolve_uring_object_path`, a blocking
helper called inside both `spawn_blocking` closures. Each caller keeps exactly
what differs — its open flags, its error type, its metadata/bounds/align
handling — and no longer restates the resolution. No behavior change: the same
checks run in the same order and produce the same errors (the O_DIRECT path
still maps them through `DirectOpenError::Disk`).

Net -12 lines. Verified on a real Linux host (16-core, real io_uring):
clippy -p rustfs-ecstore --all-targets -D warnings clean; disk::local tests
144 passed, 0 failed — including the io_uring, O_DIRECT, fd-cache, and
page-cache-reclaim cases that exercise both read paths.

Co-authored-by: heihutu <heihutu@gmail.com>

2026-07-10 17:03:34 +00:00

benches

refactor: segment residual storage api boundaries (#3905 )

2026-06-26 15:56:38 +08:00

docs

refactor: use canonical Rust module paths (#4269 )

2026-07-05 03:01:14 +08:00

src

refactor(ecstore): extract the shared io_uring read preamble (backlog#1145) (#4696 )

2026-07-10 17:03:34 +00:00

tests

test(interop): add real MinIO read and migration parity tests (#4377 )

2026-07-08 01:12:49 +08:00

AGENTS.md

chore(agents): add Rust code quality rules and skill (#3144 )

2026-05-31 22:19:36 +08:00

build.rs

refactor: Restructure project layout and clean up dependencies (#30 )

2025-07-02 19:33:12 +08:00

Cargo.toml

feat(ecstore): run one io_uring ring per shard on each disk (backlog#1145) (#4653 )

2026-07-10 07:41:11 +00:00

README.md

fix: revert standalone #2351 artifacts (phase 5) (#2535 )

2026-04-14 22:35:05 +08:00

run_benchmarks.sh

fix(get): remove GET chunk fast path (#2507 )

2026-04-12 23:12:23 +08:00

README.md

RustFS ECStore - Erasure Coding Storage

High-performance erasure coding storage engine for RustFS distributed object storage

📖 Documentation · 🐛 Bug Reports · 💬 Discussions

📖 Overview

RustFS ECStore provides erasure coding storage capabilities for the RustFS distributed object storage system. For the complete RustFS experience, please visit the main RustFS repository.

✨ Features

Reed-Solomon erasure coding implementation
Configurable redundancy levels (N+K schemes)
Automatic data healing and reconstruction
Multi-drive support with intelligent placement
Parallel encoding/decoding for performance
Efficient disk space utilization

📚 Documentation

For comprehensive documentation, examples, and usage guides, please visit the main RustFS repository.

📄 License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Copyright 2024 RustFS Team

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

RustFS is a trademark of RustFS, Inc.
All other trademarks are the property of their respective owners.

Made with ❤️ by the RustFS Storage Team