Agent-Skills.md

Agent Skills: SeaweedFS

SeaweedFS distributed storage. Covers filer, S3 API, replication, cloud tiers, and operations. Use when deploying SeaweedFS, configuring filer stores, exposing S3-compatible endpoints, or planning backup and security controls. Keywords: SeaweedFS, weed, filer, S3, object storage.

UncategorizedID: itechmeat/llm-code/seaweedfs

Repository

itechmeat/llm-code
itechmeatLicense: MIT
11

Install this agent skill to your local

pnpm dlx add-skill https://github.com/itechmeat/llm-code/tree/HEAD/skills/seaweedfs

Skill Files

Browse the full folder contents for seaweedfs.

Download Skill

Loading file tree…

skills/seaweedfs/SKILL.md

Skill Metadata

Name
seaweedfs
Description
"SeaweedFS distributed storage. Covers filer, S3 API, replication, cloud tiers, and operations. Use when deploying SeaweedFS, configuring filer stores, exposing S3-compatible endpoints, or planning backup and security controls. Keywords: SeaweedFS, weed, filer, S3, object storage."

SeaweedFS

This skill is a practical router for deploying and operating SeaweedFS from the upstream repository and wiki.

Prefer production guidance from multi-component setups over weed mini shortcuts.

Quick Navigation

| Situation | Open | | ----------------------------------------------------- | ------------------------------------------------------------------ | | Learn the system shape and bootstrap paths | references/getting-started.md | | Stand up a local all-in-one sandbox | references/quick-start-mini.md | | Review control-plane, volume, and collection topology | references/topology-and-setup.md | | Check master, volume, filer, and client API surfaces | references/api-surfaces.md | | Set replication, TTL, failover masters, and env vars | references/configuration.md | | Work with performance notes, FAQ topics, and examples | references/benchmarks-and-use-cases.md | | Work with filer metadata, uploads, JWT, and TUS | references/filer-core.md | | Choose and scale filer metadata stores | references/filer-stores.md | | Operate S3 buckets, auth, and IAM/OIDC | references/s3-gateway.md | | Plan Cloud Drive and remote storage mounts | references/cloud-drive.md | | Run backups, metrics, repairs, and shell workflows | references/backup-and-replication.md, references/operations.md | | Choose S3 encryption and client tooling | references/encryption.md, references/s3-client-tools.md | | Review transport, JWT, TLS, and exposure controls | references/security.md |

When to Use

  • Planning a SeaweedFS deployment
  • Running weed components in development or production
  • Designing filer, S3, or cloud-tier topologies
  • Choosing metadata stores and replication patterns
  • Hardening SeaweedFS for public or multi-tenant use
  • Operating backups, metrics, and cluster repair workflows

Core Mental Model

  • SeaweedFS separates volume management from file and object access paths.
  • The filer layer adds directories, metadata stores, and higher-level protocols.
  • S3, WebDAV, FUSE, and other interfaces are front doors on top of the same storage services.
  • Production deployments should document topology, credentials, persistence, monitoring, and recovery paths explicitly.

Release Highlights (4.25)

  • Security/admin path: 4.24-4.25 tightens admin auth on destructive/admin endpoints and fixes Admin UI behavior under security.toml by attaching admin-signed auth on filer IAM gRPC calls.
  • Erasure coding / multi-disk ops: the release line fixes several EC planner/recovery cases across multi-disk and cross-server layouts, including stale-shard cleanup and safer source-volume deletion.
  • S3/IAM hardening: IAM users without policies are now denied instead of implicitly over-permitted, while OIDC/web-identity and audit surfaces continue to mature.

Release Highlights (4.26 -> 4.28)

  • Erasure coding / multi-disk ops: EC planning now packs shards across disks more reliably, includes disk_id in execution planning, and can rebuild lost .ecx / .vif metadata from local shards during recovery.
  • Integrity checks: scrubbing/fsck paths now account for zero-sized volumes instead of silently skipping them, which matters for sparse or recently created topologies.
  • Filer backend reliability: Redis3 avoids a skiplist-end panic path, and SQL-based filer stores no longer force-disable idle connection pooling.
  • S3 audit trail: requester identity is populated more consistently for GET/HEAD/IAM operations, improving compliance and incident triage.
  • HA heartbeat path: masters now accept volume-server ping targets on follower replicas, which improves failover visibility in multi-master deployments.

Release Highlights (4.31 -> 4.33)

  • S3 versioning/IAM: atomic versioned PutObject commits, proper NoSuchVersion errors, latest-pointer repair and recovery, suspended-versioning delete handling, managed IAM policy versions, and bucket read-only quota enforcement; 4.33 also fixes HTTP-date conditionals, checksum trailer headers, and empty v4 signed header names.
  • Erasure coding integrity: per-shard checksum sidecars for bitrot detection (4.31), even shard spreading across machines with co-located servers treated as a single fault domain and pre-deletion shard-landing verification (4.32), and guards preventing EC shards from different encode runs mixing or leaving phantom .dat on restart (4.33).
  • Volume server: fixes maxVolumeCount dead zone on auto-sized disks, keeps volumes writable after deletion-tail compaction, resolves EC data-shard count from .vif on reboot (4.31), and adds CheckDisk disk-health detection (4.32).
  • Filer scalability: bounded BFS-metadata memory and byte-lexicographic S3 list order (4.31), streamed metadata-subscription log files (4.32), and object-size distribution metrics, mount-reconnect OOM fixes, per-chunk replay, a bounded flush queue, and Elasticsearch 8 (elastic8) support (4.33).
  • Admin/worker: lane-aware scheduler pruning, -dataDir defaulting for persisted state and in-flight task reload on startup (4.32), plus full cluster volume list JSON export (4.33).
  • Rust volume server: bounded request body / stored-content expansion to prevent OOM under load (4.31); stops EC-shard-deletion phantom .dat on restart (4.33).

Release Highlights (4.29 -> 4.30)

  • S3 write/auth path: object writes move toward filer-side owner routing and ObjectTransaction batches, reducing distributed-lock pressure; 4.30 also tightens path traversal rejection, ownership-control validation, MetadataDirective=REPLACE, and JWT handling for unsigned-streaming uploads.
  • FUSE and filer coordination: POSIX advisory locks are now routed through filer ownership under -dlm, with session leases, keepalive, ring-change cooling, and writeback-cache crash fixes for cross-mount write workloads.
  • Erasure coding and volume repair: EC placement uses the shared ecbalancer.Place path and placement snapshots, while 4.30 improves credible-replica selection, empty-stub cleanup, .vif preservation, writable-volume notification after vacuum, and shell safety around stuck read-only volumes and merge verification.
  • Operations surfaces: admin exposes Prometheus metrics, and S3/IAM/volume/filer/master processes add /healthz and /readyz probes for orchestration checks.
  • Filer, sync, and remote sinks: Redis2 now applies keyPrefix in KV methods, Postgres filer writes default to ON CONFLICT upsert, dropped filers are pruned from discovery, and sync/remote-storage paths preserve chunk size, manifest, offset, and MIME metadata more reliably.

Release Highlights (4.20)

  • S3/IAM: embedded IAM flows gained ListUserPolicies, group inline policy actions, safer user-policy round trips, and bucket-scoped cleanup on DeleteBucket.
  • Mount/FUSE: weed mount adds -dlm for cross-mount write coordination and improves POSIX metadata behavior, nlink accounting, and filer RPC efficiency.
  • Master placement: volume assignment is more size-aware, readonly transitions drain pending size first, and a topology bug that could cause endless growth in some DC/rack layouts was fixed.
  • Filer reliability: PgBouncer/Postgres compatibility improved, graceful shutdown corruption was fixed, and redundant filer disk reads that caused memory/CPU regressions were removed.
  • Ops surfaces: weed shell gained group-management helpers, S3 user provisioning handles existing users more safely, and master/volume now export start_time_seconds metrics.

Prohibitions

  • Do not use weed mini for production.
  • Do not treat single-binary defaults as production-safe configuration.
  • Do not expose S3 or filer endpoints publicly before reviewing auth, TLS, and network boundaries.
  • Do not choose a filer store without validating HA, scaling, and backup properties.
  • Do not design backup or replication flows without restore validation.

Links