diff --git a/manual/extension/metadata-server.md b/manual/extension/metadata-server.md
index 9901f2cb..3811c3da 100644
--- a/manual/extension/metadata-server.md
+++ b/manual/extension/metadata-server.md
@@ -104,10 +104,6 @@ docker compose up -d
         [md-server] [2025-01-24 06:23:44] [INFO] Database initialization completed
         [md-server] [2025-01-24 06:23:44] [INFO] Configuration file generated
         ```
-    - `$SEAFILE_VOLUME/seafile/logs/seaf-md-server.log`
-        ```log
-        [2025-02-23 06:07:57] [INFO] starting seaf-md-server
-        ```
     - `$SEAFILE_VOLUME/seafile/logs/seafevents.log`
         ```log
         [2025-02-23 06:08:05] [INFO] seafevents.repo_metadata.index_worker:134 refresh_lock refresh_thread Starting refresh locks
@@ -122,4 +118,4 @@ docker compose up -d
 When you deploy Seafile server and Metadata server to the **same machine**, Metadata server will use the same persistence directory (e.g. /opt/seafile-data) as Seafile server. Metadata server will use the following directories or files:
 
 - `/opt/seafile-data/seafile/md-data`: Metadata server data and cache
-- `/opt/seafile-data/seafile/logs/seaf-md-server.log`: The running log file of Metadata server
+- `/opt/seafile-data/seafile/logs/seaf-md-server`: The logs directory of Metadata server, consist of a running log and an access log.