9 Commits

Include renames

Author	SHA1	Message	Date
Chris Lu	e7be6bb2f8	filer: allow clearing a bucket read-only flag stuck after quota removal (#10310) ... * filer: allow clearing a bucket read-only flag stuck after quota removal Once s3.bucket.quota.enforce marks a bucket read-only, removing or disabling the quota orphans the flag: enforcement skips buckets with a non-positive quota, and fs.configure merges booleans with OR so -readOnly=false could never turn it off. The only way out was deleting the whole path rule. - s3.bucket.quota -op=remove/disable and the admin server quota update now lift the read-only flag on the bucket's path rule - fs.configure now honors explicitly passed false boolean flags (-readOnly, -fsync, -worm) instead of OR-merging them away * filer: ClearBucketReadOnly reports unchanged when the save fails	2026-07-10 22:09:39 -07:00
Chris Lu	69553e5ba6	convert error fromating to %w everywhere (#6995)	2025-07-16 23:39:27 -07:00
Aleksey Kosovandakosov	165af32d6b	added context to filer_client method calls (#6808) ... Co-authored-by: akosov <a.kosov@kryptonite.ru>	2025-05-22 09:46:49 -07:00
chrislu	ec30a504ba	refactor	2024-09-29 10:38:22 -07:00
chrislu	701abbb9df	add IsResourceHeavy() to command interface	2024-09-28 20:23:01 -07:00
chrislu	26dbc6c905	move to https://github.com/seaweedfs/seaweedfs	2022-07-29 00:17:28 -07:00
guol-fnst	5bc895673e	add getting bucket quota	2022-07-04 15:36:44 +08:00
guol-fnst	dd4664e610	fix usage	2022-07-04 11:31:39 +08:00
chrislu	606667f205	able to configure the quota for a bucket	2022-01-21 01:42:20 -08:00