Skip to content

Add whatokk Lab9 MinIO report #4

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.

Sign up for GitHub

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

Open
whatokk wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add whatokk Lab9 MinIO report #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
87c2b5c
Add whatokk Lab9 MinIO report PDF
whatokk Jun 11, 2026
25ca822
Update student name to Jiang Chengjun [skip ci]
whatokk Jun 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added reports/whatokk_Lab9.pdf
View file
Open in desktop
Binary file not shown.
16 changes: 16 additions & 0 deletions reports/whatokk_Lab9_experiment_record.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Lab9 Experiment Record

- Experiment: Distributed Object Storage & Fault Tolerance Testing
- Repository: https://github.com/whatokk/lab9-distributed-object-storage
- Successful Actions run: https://github.com/whatokk/lab9-distributed-object-storage/actions/runs/27364710248
- Execution environment: GitHub Actions Ubuntu runner
- Storage simulation: MinIO with four mounted directories data1, data2, data3, data4
- Bucket: my-cloud-storage
- Test object: bigfile.bin, 20 MiB
- Fault simulation: stopped cluster, deleted and recreated data3, restarted cluster
- Result: object remained accessible; original and recovered files had identical SHA256 hash
- Generated at: 2026-06-12 01:25:22 +08:00

## Key Results

MinIO distributed storage split object data and metadata across all four storage directories. After data3 was removed and recreated, the object `bigfile.bin` was still listed and readable. The SHA256 hashes of `bigfile.bin` and `recovered-bigfile.bin` matched exactly, verifying fault tolerance through erasure coding and distributed redundancy.