From 747cfe232f70780cd5f35174340075d19e2cf8f1 Mon Sep 17 00:00:00 2001 From: Andreas Dilger Date: Wed, 12 Oct 2016 00:12:11 -0600 Subject: [PATCH] LUDOC-11 changelog: describe changelog space usage Clarify under changelog registration that this consumes space on the MDT, and if there is no changelog user that this can fill all space on the MDT eventually. Signed-off-by: Andreas Dilger Change-Id: I4f216a77a66e2f4b17d2c2378112f57dfd7e5f2d Reviewed-on: http://review.whamcloud.com/23097 Tested-by: Jenkins Reviewed-by: Joseph Gmitter --- SystemConfigurationUtilities.xml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/SystemConfigurationUtilities.xml b/SystemConfigurationUtilities.xml index 40a179d..b3c1fc7 100644 --- a/SystemConfigurationUtilities.xml +++ b/SystemConfigurationUtilities.xml @@ -601,7 +601,14 @@ $ lctl conf_param testfs.llite.max_read_ahead_mb=16 changelog_register - Registers a new changelog user for a particular device. Changelog entries are not purged beyond a registered user's set point (see lfs changelog_clear). + Registers a new changelog user for a particular device. + Changelog entries are saved persistently on the MDT with each + filesystem operation, and are only purged beyond all registered + user's minimum set point (see + lfs changelog_clear). This may cause the + Changelog to consume a large amount of space, eventually + filling the MDT, if a changelog user is registered but never + consumes those records. @@ -609,7 +616,10 @@ $ lctl conf_param testfs.llite.max_read_ahead_mb=16 changelog_deregister id - Unregisters an existing changelog user. If the user's "clear" record number is the minimum for the device, changelog records are purged until the next minimum. + Unregisters an existing changelog user. If the + user's "clear" record number is the minimum for + the device, changelog records are purged until the next minimum. + -- 1.8.3.1