From 88ea6a0e84b196d3e6768516a68129bf9de6140d Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Sat, 29 Nov 2025 10:13:35 -0800 Subject: [PATCH] Update FAQ.md --- FAQ.md | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/FAQ.md b/FAQ.md index c4d7a4b..1277caa 100644 --- a/FAQ.md +++ b/FAQ.md @@ -113,7 +113,7 @@ To upgrade to `large disk` version, * start master with a larger volume size limit * start volume servers, with reasonable maximum number of volumes -**What's the difference between `large_disk` and `large_disk_full`?** +### What's the difference between `large_disk` and `large_disk_full`?** - **`large_disk`**: Normal volumes are limited to 30GB each. This `large_disk` build enables support for volumes larger than 30GB (the `5BytesOffset` flag). It uses 17 bytes per file entry instead of 16 bytes, allowing volume sizes up to 8TB. @@ -136,19 +136,6 @@ To upgrade to `large disk` version, - Use **`_large_disk_full`** if you need both large volumes AND extra filer store backends. - Use **`_large_disk_rocksdb`** if you specifically need RocksDB as a filer store with large disk support. -**Example Docker commands:** - -```bash -# Standard build -docker run chrislusf/seaweedfs:latest server - -# Large disk build -docker run chrislusf/seaweedfs:3.79_large_disk server - -# Large disk with full backend support -docker run chrislusf/seaweedfs:3.79_large_disk_full server -``` - **Important:** The `large_disk` versions are NOT compatible with standard 30GB versions. You cannot mix them in the same cluster. See the section above for migration instructions. ### How large should I configure the volumes?