ECS: xDoctor: RAP007: Symptom Code: 2028: Root File System Low Disk Space

Summary: ECS: xDoctor: RAP007: SymptomCode: 2028: Root File System Low Disk Space

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Beginning in ECS xDoctor v4.8‑108.0 and ObjectScale xDoctor v5.1‑108.0, RAP007 (LVRoot too full) is implemented as an auto healer. When the root filesystem exceeds the Error or Critical threshold, xDoctor raises a RAP007 alert and automatically invokes its built‑in repair orchestration process to perform the necessary cleanup (when xDoctor auto healers are enabled).

 

Note:  If your deployment is running an xDoctor version below 108, the auto healer is not available. You must use the Auto Pilot process described below or perform the manual remediation steps provided in the resolution section.

 

Alert That Triggers RAP007 Auto‑Healing

This alert is generated the moment root filesystem usage crosses the severity threshold and is what initiates the auto‑healer workflow.

RAP007: File system root (/)(RFS) low disk space

  • LVRoot too full
  • One of the RFS resources exceeded a certain severity threshold.
  • RAP007
  • RAP 007
  • SymptomCode: 2028

Alert Output Example: 

Note: All version prior to ECS xDoctor v4.8‑108.0 and ObjectScale xDoctor v5.1‑108.0 will just alert on this issue.

------------------------------------------------------
ERROR - (Cached) File system root (/) - low disk space
------------------------------------------------------
Node      = 169.254.1.1
Extra     = {'169.254.1.1': {'169.254.1.1': '82'}}
RAP       = RAP007
Solution  = KB 469957
Timestamp = 2026-02-06_144748
PSNT      = CKM00000000000 @ 4.8-108.0

  

  
Auto Healer Remediation (Example)

  
When auto healers are enabled, xDoctor attempts immediate cleanup and reports the reclaimed space.

  

  

  
---------------------------------------------
FIXED - Auto Healer fixed root_low_disk_space
---------------------------------------------
Node      = Nodes
Extra     = {"Nodes": {
"169.254.1.2": " Before cleanup available space: 143G used percentage: 84%. After cleanup available space: 786G / used percentage: 12%. Space reclaimed: 643.0G.", 
"169.254.1.3": " Before cleanup available space: 143G used percentage: 84%. After cleanup available space: 809G / used percentage: 9%. Space reclaimed: 666.0G.", 
"169.254.1.4": " Before cleanup available space: 145G used percentage: 84%. After cleanup available space: 810G / used percentage: 9%. Space reclaimed: 665.0G.", 
"169.254.1.5": " Before cleanup available space: 142G used percentage: 84%. After cleanup available space: 805G / used percentage: 10%. Space reclaimed: 663.0G."}}

  



  
Auto healer Requirement

  
Auto healers must be enabled during installation or after installation using KB: ECS: xDoctor: How to Enable xDoctor Auto Healer after tool installation

  
 

  
Manual Validation Steps:

  
Examine the output of the affected node:

  

   Command:
   
df -k /

   
Example:
  

  
admin@node1:~> df -k /
Filesystem             1K-blocks      Used Available Use% Mounted on
/dev/mapper/ECS-LVRoot 459425792 373686300  85739492  82% /


  


   Confirm this command output of the affected node for a human readable format:

  

   Command:
   
df -h /

   
Example:
  

  
admin@node1:~> df -h /
Filesystem              Size  Used Avail Use% Mounted on
/dev/mapper/ECS-LVRoot  439G  357G   82G  82% /


  



   Confirm that the RFS size on the other nodes is below 80%.

  

   Command:
   
svc_exec "df -h | grep LVRoot"

   
Example:
  

  
admin@node1:~> svc_exec "df -h | grep LVRoot"
svc_exec v1.0.3 (svc_tools v2.6.0)                 Started 2022-09-08 15:07:41

Output from node: r1n1 (xx.xx.xx.xxx)                 retval: 0
/dev/mapper/ECS-LVRoot  439G  357G   82G  82% /

Output from node: r1n2 (xx.xx.xx.xxx)                  retval: 0
/dev/mapper/ECS-LVRoot  439G  223G  216G  51% /

Output from node: r1n3 (xx.xx.xx.xxx)                  retval: 0
/dev/mapper/ECS-LVRoot  439G  184G  255G  42% /

Output from node: r1n4 (xx.xx.xx.xxx)                  retval: 0
/dev/mapper/ECS-LVRoot  439G  197G  242G  45% /

Output from node: r1n5 (xx.xx.xx.xxx)                  retval: 0
/dev/mapper/ECS-LVRoot  439G  167G  272G  39% /

Output from node: r1n6 (xx.xx.xx.xxx)                  retval: 0
/dev/mapper/ECS-LVRoot  439G  169G  271G  39% /

Output from node: r1n7 (xx.xx.xx.xxx)                  retval: 0
/dev/mapper/ECS-LVRoot  439G  162G  277G  37% /

Output from node: r1n8 (xx.xx.xx.xxx)                  retval: 0
/dev/mapper/ECS-LVRoot  439G  239G  200G  55% /


        
Cause

        
    
   
  • An active service request has been opened for this issue.
    • 
   
  • 
    
    
     Multiple factors can contribute to this condition, including large temporary files left behind during prior maintenance or support actions that may now require cleanup.
    
    • 
  

        
Resolution

        
xDoctor Auto Healer:  ObjectScale xDoctor v5.1‑108.0 / ECS xDoctor v4.8‑108.0 or later

  
 

  

   
    
    
  1. To manually trigger the Enabled auto healer, run the following command on the master.rack node. This initiates the rack analyzers, which will validate and auto‑heal the nodes one at a time.
    2. 
   

  

  

   Command:

  

  
# sudo xdoctor --scope=system --rap=RAP007

  
Example:

  
admin@ecsnode1:~> sudo xdoctor --scope=system --rap=RAP007
2026-02-03 22:19:43,652: xDoctor_4.8-108.0 - INFO    : Initializing xDoctor v4.8-108.0 ...
2026-02-03 22:19:44,198: xDoctor_4.8-108.0 - INFO    : Starting xDoctor session_1770157182.887 ... (system)
2026-02-03 22:19:44,388: xDoctor_4.8-108.0 - INFO    : xDoctor Composition - Analyzer(s):ac_disk_usage
2026-02-03 22:19:44,405: xDoctor_4.8-108.0 - INFO    : Session limited to 0:40:00
[... Truncated Output ...]
2026-02-03 22:19:59,328: xDoctor_4.8-108.0 - INFO    : Autohealing root_low_disk_space on node 169.254.1.5 ...
2026-02-03 22:21:16,991: xDoctor_4.8-108.0 - INFO    : Autohealing root_low_disk_space on node 169.254.1.2 ...
2026-02-03 22:22:20,250: xDoctor_4.8-108.0 - INFO    : All data analyzed in 0:02:23
2026-02-03 22:22:20,269: xDoctor_4.8-108.0 - INFO    : --------------------
2026-02-03 22:22:20,269: xDoctor_4.8-108.0 - INFO    : Diagnosis Summary
2026-02-03 22:22:20,269: xDoctor_4.8-108.0 - INFO    : --------------------
2026-02-03 22:22:20,269: xDoctor_4.8-108.0 - INFO    : PSNT: C000000000000000
2026-02-03 22:22:20,269: xDoctor_4.8-108.0 - INFO    : --------------------
2026-02-03 22:22:20,269: xDoctor_4.8-108.0 - INFO    : FIXED             =  1
2026-02-03 22:22:20,270: xDoctor_4.8-108.0 - INFO    : CRITICAL          =  0
2026-02-03 22:22:20,270: xDoctor_4.8-108.0 - INFO    : CRITICAL (CACHED) =  0
2026-02-03 22:22:20,270: xDoctor_4.8-108.0 - INFO    : ERROR             =  0
2026-02-03 22:22:20,270: xDoctor_4.8-108.0 - INFO    : ERROR (CACHED)    =  0
2026-02-03 22:22:20,270: xDoctor_4.8-108.0 - INFO    : WARNING           =  1
2026-02-03 22:22:20,270: xDoctor_4.8-108.0 - INFO    : INFO              =  0
2026-02-03 22:22:20,270: xDoctor_4.8-108.0 - INFO    : VERBOSE           =  0
2026-02-03 22:22:20,270: xDoctor_4.8-108.0 - INFO    : REPORT            =  0
2026-02-03 22:22:20,386: xDoctor_4.8-108.0 - INFO    : ---------------------
[... Truncated Output ...]
2026-02-03 22:22:26,595: xDoctor_4.8-108.0 - INFO    : Session Report                - sudo xdoctor --report --archive=2026-02-03_221942
[... Truncated Output ...]
2026-02-03 22:22:26,615: xDoctor_4.8-108.0 - INFO    : xDoctor session_1770157182.887 finished in 0:02:43
2026-02-03 22:22:26,635: xDoctor_4.8-108.0 - INFO    : Successful Job:1770157182 Exit Code:196

  

   
 

   
    
    
  1. Run the session report to review the results of the manual auto‑heal execution.
    2. 
   

  

  

   

    Command: 
   

   

    Note: Use the Session Report command provided in the xDoctor example above to review the results of the manual auto‑heal execution.
   

  

  
# sudo xdoctor --report --archive=<session report>

  
Example:

  
admin@ecsnode1:~> sudo xdoctor --report --archive=2026-02-03_221942

xDoctor 4.8-108.0
CKM00000000000 - ECS 3.8.1.4

Displaying xDoctor Report (2026-02-03_221942) Filter:[] ...

---------------------------------------------
FIXED - Auto Healer fixed root_low_disk_space
---------------------------------------------
Node      = Nodes
Extra     = {"Nodes": {"169.254.1.2": " Before cleanup available space: 76G used percentage: 83%. After cleanup available space: 126G / used percentage: 72%. Space reclaimed: 50.0G.", "169.254.1.5": " Before cleanup available space: 81G used percentage: 82%. After cleanup available space: 137G / used percentage: 69%. Space reclaimed: 56.0G."}}
Timestamp = 2026-02-03_221942
PSNT      = CKM00000000000 @ 4.8-108.0


  

    
  

  
xDoctor Auto Pilot:

  
This knowledge base (KB) is now automated with xDoctor Auto Pilot addressing most issues without the need for support involvement.


   This feature is native to xDoctor 4-8.104.0 and above, for syntax and usage issues reference ECS: ObjectScale: How to run KB Automation Scripts (Auto Pilot).


   To find the master node of the rack:

  
  Command:

  
ssh master.rack

  
To find the NAN IP, use the ip identified in the alert or from the command below:

  
getrackinfo

  
 Example:

  
admin@ecsnode1:~> getrackinfo
Node private      Node              Public                                BMC
Ip Address        Id       Status   Mac                 Ip Address        Mac                 Ip Address        Private.4(NAN)    Node Name
===============   ======   ======   =================   ===============   =================   ===============   ===============   =========
192.168.219.1     1        MA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.101   169.254.1.1       provo-red
192.168.219.2     2        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.102   169.254.1.2       sandy-red
192.168.219.3     3        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.103   169.254.1.3       orem-red
192.168.219.4     4        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.104   169.254.1.4       ogden-red
192.168.219.5     5        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.105   169.254.1.5       layton-red
192.168.219.6     6        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.106   169.254.1.6       logan-red
192.168.219.7     7        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.107   169.254.1.7       lehi-red
192.168.219.8     8        SA       00:00:00:00:00      0.0.0.0           00:00:00:00:00      192.168.219.108   169.254.1.8       murray-red

  
 

  
    
   
  1. Run the automation command from a primary node with xDoctor 4-8.104.0 and above.
    2. 
  

  

   Command: 
  

  

               Note: Only --target-node is supported for this action.
  

  
 sudo xdoctor autopilot --kb 79798 --target-node <NAN IP>

  

Example:

  
admin@ecsnode1:~>sudo xdoctor autopilot --kb 79798 --target-node 169.254.1.1
Checking for existing screen sessions...
Starting screen session 'autopilot_kb_79798_20260203_215645'...
Screen session 'autopilot_kb_79798_20260203_215645' started successfully.
Return code: 0
Attaching to screen session 'autopilot_kb_79798_20260203_215645'...

  
    
   
  1. 
    
    
     Review and acknowledge the actions that will be performed and optionally display the list of files that will be deleted before proceeding.
    
    2. 
  

  

   Command:
   
# yes or no
   
Example of Acknowledgement Prompt:
  

  
TASK [Prompt for acknowledgement] *************************************************************************************************************************************************************
[Prompt for acknowledgement]
════════════════════════════════════════════════════════════════════════════════
This Automated Knowledge Base (KB) will identify and remove frequently encountered files from the ObjectScale and ECS, aiming to safely reclaim space in the root file system. To proceed, you can review or delete the files on the system.
════════════════════════════════════════════════════════════════════════════════
Would you like to proceed with the steps by typing 'Yes' or 'Y', or skip the review and deletion actions by typing 'No' or 'N'?
════════════════════════════════════════════════════════════════════════════════
(Y) Yes
(N) No
════════════════════════════════════════════════════════════════════════════════
: 


  

   Example of optional file listing prompt:
  

  
════════════════════════════════════════════════════════════════════════════════
To proceed, type 'Yes' to list all files found or 'No' to exclude file listing from the output.
════════════════════════════════════════════════════════════════════════════════
(Y) Yes
(N) No
════════════════════════════════════════════════════════════════════════════════
:


  
 

  

   Example of optional file listing:
  

  
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ 2026-02-03 22:05:15 TASK OK: Summary of all logs to delete and/or truncate files
│ 2026-02-03 22:05:15 [169.254.1.1] => OK
│ *******************************************************************************
│ OS, support, oc_map, Fabric and Lifecycle logs pre-delete summary list:
│ *******************************************************************************
│ *******************************************************************************
│ List of ObjectScale / ECS OS logs older than 30 days to be deleted:
│ *******************************************************************************
│ List of fabric agent logs older than 7 days to be deleted:
│ /opt/emc/caspian/fabric/agent/log/agent.log.01242026-152610.gz
│ /opt/emc/caspian/fabric/agent/log/agent.log.01252026-202127.gz
│ /opt/emc/caspian/fabric/agent/log/agent.log.01272026-011722.gz
│ *******************************************************************************
│ List of lifecycle logs older than 7 days to be deleted:
│ /opt/emc/caspian/fabric/agent/services/fabric/lifecycle/log/lifecycle.log.01232026-221706.gz
│ /opt/emc/caspian/fabric/agent/services/fabric/lifecycle/log/lifecycle.log.01252026-114038.gz
│ /opt/emc/caspian/fabric/agent/services/fabric/lifecycle/log/lifecycle.log.01262026-203616.gz
│ /opt/emc/caspian/fabric/agent/services/fabric/lifecycle/log/lifecycle.log.01272026-184114.gz
│ *******************************************************************************
│ List of service .out files over 500 MiB to be truncated:
│ *******************************************************************************
│ List of crash files to be deleted:
│ *******************************************************************************
│ List of support log files to be deleted:
│ *******************************************************************************
│ List of old tool installation packages to be deleted:
│ /home/admin/xDoctor4ECS-5.1-107.0.noarch.rpm
│ *******************************************************************************
│ oc_map chk logs to be deleted:
│ *******************************************************************************
│ oc_map retry logs to be deleted:
│ *******************************************************************************
│ oc_map results logs to be deleted:
│ *******************************************************************************
│ Root ssd system file system clean up pre-delete summary:
│ *******************************************************************************
│ *******************************************************************************
│ 30+ day old ObjectScale / ECS OS logs total size pending deletion: 0 Bytes
│ 7+ day old fabric agent logs total size pending deletion: 5.1 MB
│ 7+ day old lifecycle logs total size pending deletion: 10.6 MB
│ ObjectScale / ECS service .out logs larger than 500 mb total size pending reclaimed: 0 Bytes
│ Support logs total size pending deletion: 0 Bytes
│ Crash file(s) pending deletion: 0 Bytes
│ *******************************************************************************
│ Before cleanup available space / used percentage: 703G 21%
│ *******************************************************************************
│ IMPORTANT! If capacity reduction is not successful you must review the below folders with SR owners and Jira for possible deletion:
│ *******************************************************************************
│ List of OE/CE/SR directories to review and manually clean after confirming they are safe to remove:
│ *******************************************************************************
│ 0 /tmp/ECSOE-12345
│ 24K /tmp/ECSOE-21827
│ 0 /tmp/SR
│ 0 /tmp/SR123456789
│ *******************************************************************************
│ List of home directories sizes and top 10 subdirectory files to review and manually clean after confirming they are safe to remove:
│ *******************************************************************************
│ Top 5 home directories by size:
│ *******************************************************************************
│ Review the sizes of the home directories listed below.
│ If a home directory is consuming a large amount of space, then that path must be investigated.
│ *******************************************************************************
│ 17G /home/admin
│ 48K /home/emc
│ 8.0K /home/service
│ *******************************************************************************
│ Top 10 subdirectory files under home to review for deletion:
│ ==> Below are the top 10 subdirectory files within the home directories.
│ ==> Review and manually clean these files after confirming they are safe to remove.
│ *******************************************************************************
│ 3.6G /home/admin/ecs-os-firmware-dell-1.3.0.0-0.zip
│ 3.6G /home/admin/ecs-os-firmware-dell-1.2.0.0-0.zip
│ 3.6G /home/admin/1.31.0.0-0
│ 3.6G /home/admin/1.2.0.0-0
│ 1018M /home/admin/DO_NOT_REMOVE_toroi_bundle.tar.gz
│ 195M /home/admin/rescue.tar
│ 195M /home/admin/images
│ 171M /home/admin/toroi-96.8212.30
│ 155M /home/admin/transfer
│ 108M /home/admin/xDoctor4ECS-5.1-108.0.noarch.rpm
│ *******************************************************************************
│ List of oc_map dmp logs to review cluster history in SR and/or Jira to confirm it is safe to delete the file(s):
│ *******************************************************************************
│ IMPORTANT! Below is the node's vnest summary. If it is consuming over 100 GB of the node's SSD capacity, Open an SR with Dell ObjectScale / ECS support.
│ *******************************************************************************
│ vnest is below 100 gigabytes Folder path: /opt/emc/caspian/fabric/agent/services/object/data/vnest/vnest-main/index, Size: 1.8G
│ *******************************************************************************
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

  
    
   
  1. Confirm to delete the files listed above:
    2. 
  

  
Command:

  
# yes or no

  
Example:

  
════════════════════════════════════════════════════════════════════════════════
Confirm Delete and/or Truncate on all the files listed above.
════════════════════════════════════════════════════════════════════════════════
Would you like to proceed with the steps by typing 'Yes' or 'Y', or abort deletion actions by typing 'No' or 'N'?
════════════════════════════════════════════════════════════════════════════════
(Y) Yes
(N) No
════════════════════════════════════════════════════════════════════════════════
:


  
    
   
  1. Review summary for deleted files and RFS savings from the execution:
    2. 
  

  
Example:

  
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ 2026-02-03 22:08:42 TASK OK: Print summary
│ 2026-02-03 22:08:42 [169.254.1.1] => OK
│ *******************************************************************************
│ Root file system clean up summary:
│ *******************************************************************************
│ *******************************************************************************
│ 30+ day old ObjectScale / ECS OS logs total size deleted: 0 Bytes
│ 7+ day old fabric agent logs total size deleted: 5.1 MB
│ 7+ day old lifecycle logs total size deleted: 10.6 MB
│ ObjectScale / ECS service .out logs larger than 500 mb total size reclaimed: 0 Bytes
│ Support logs total size deleted: 0 Bytes
│ Total disk space reclaimed from old tool packages: 111.8 MB
│ Crash file(s) deleted: 0 Bytes
│ *******************************************************************************
│ Before cleanup available space / used percentage: 703G 21%
│ After cleanup available space / used percentage: 703G 21%
│ *******************************************************************************
│ oc_map log deletion summary:
│ *******************************************************************************
│ oc_map chk logs total size deleted: 0 Bytes
│ oc_map retry logs total size deleted: 0 Bytes
│ oc_map results logs total size deleted: 0 Bytes
│ *******************************************************************************
│ IMPORTANT! If capacity reduction is not successful you must review the below folders with SR owners and Jira for possible deletion:
│ *******************************************************************************
│ List of OE/CE/SR directories to review and manually clean after confirming they are safe to remove:
│ *******************************************************************************
│ 0 /tmp/ECSOE-12345
│ 24K /tmp/ECSOE-21827
│ 0 /tmp/SR
│ 0 /tmp/SR123456789
│ *******************************************************************************
│ List of home directories sizes and top 10 subdirectory files to review and manually clean after confirming they are safe to remove:
│ *******************************************************************************
│ Top 5 home directories by size:
│ *******************************************************************************
│ Review the sizes of the home directories listed below.
│ If a home directory is consuming a large amount of space, then that path must be investigated.
│ *******************************************************************************
│ 17G /home/admin
│ 48K /home/emc
│ 8.0K /home/service
│ *******************************************************************************
│ Top 10 subdirectory files under home to review for deletion:
│ ==> Below are the top 10 subdirectory files within the home directories.
│ ==> Review and manually clean these files after confirming they are safe to remove.
│ *******************************************************************************
│ 3.6G /home/admin/ecs-os-firmware-dell-1.3.0.0-0.zip
│ 3.6G /home/admin/ecs-os-firmware-dell-1.2.0.0-0.zip
│ 3.6G /home/admin/1.31.0.0-0
│ 3.6G /home/admin/1.2.0.0-0
│ 1018M /home/admin/DO_NOT_REMOVE_toroi_bundle.tar.gz
│ 195M /home/admin/rescue.tar
│ 195M /home/admin/images
│ 171M /home/admin/toroi-96.8212.30
│ 155M /home/admin/transfer
│ 108M /home/admin/xDoctor4ECS-5.1-108.0.noarch.rpm
│ *******************************************************************************
│ List of oc_map dmp logs to review cluster history in SR and/or Jira to confirm it is safe to delete the file(s):
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/11-12-2025/11-49-37_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/11-12-2025/11-57-26_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/11-12-2025/11-59-47_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/01-27-2026/21-19-33_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/01-27-2026/21-20-08_B1_shep_shep_ob_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/01-27-2026/21-21-42_B1_shep_shep_ob_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/01-27-2026/21-23-25_B1_shep_shep_ob_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/01-27-2026/21-24-21_B1_shep_shep_ob_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/01-27-2026/21-34-25_B1_shep_shep_ob_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/01-27-2026/21-35-26_B1_shep_shep_ob_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/01-27-2026/21-36-34_B1_shep_shep_ob_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/07-17-2025/13-25-26_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/07-17-2025/13-26-02_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/08-26-2025/14-16-11_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/08-26-2025/14-19-22_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/08-26-2025/14-27-21_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/09-09-2025/18-36-05_B1_ALL_NAMESPACES_ALL_BUCKETS_ob_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/11-18-2025/11-33-31_rt_dmp.log
│ /opt/emc/xdoctor/tools/ee_scripts/oc_map/suite/oc_cache/11-18-2025/11-33-54_rt_dmp.log
│ DMP logs total size: 27.2 kB
│ *******************************************************************************
│ IMPORTANT! Below is the node's vnest summary. If it is consuming over 100 GB of the node's SSD capacity, Open an SR with Dell ObjectScale / ECS support.
│ *******************************************************************************
│ vnest is below 100 gigabytes Folder path: /opt/emc/caspian/fabric/agent/services/object/data/vnest/vnest-main/index, Size: 1.8G
│ *******************************************************************************
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ 2026-02-03 22:08:42 TASK OK: Set fact for root FS cleanup summary
│ 2026-02-03 22:08:42 [169.254.1.1] => OK
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ NODE AUTOMATION SUMMARY:
├─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ HOST                   ok    changed   unreachable   failed   skipped   rescued   ignored
├─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ 169.254.1.1            95          3             0        0        61         0         0
│ localhost               8          0             0        0         9         0         0
├─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ Status: PASS
│ Time Elapsed: 0h 11m 55s
│ Debug log: /tmp/autopilot/log/autopilot_79798_20260203_215645.log
│ Message:   Less than or equal to 3% of space was reclaimed. Please review the automation logs to determine the top consumer of the root filesystem. Before cleanup available space: 703G used percentage:
│ 21%. After cleanup available space: 703G / used percentage: 21%. Space reclaimed: 0.0G.
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────



            


        

        
        
Affected Products

        ECS Appliance
    
Products

        ECS Appliance, ECS Appliance Hardware Gen1 U-Series, ECS Appliance Software with Encryption, ECS Appliance Software without Encryption







                        

                            

    

        

            

                
                    
 Article Properties

                
            

            

                

                        
Article Number: 000079798

                

                
                

                        
Article Type: Solution

                

                

                        
Last Modified: 05 Feb 2026


                

                    

                            
Version:  18

                    


            


        

    

    

        

            

                
                    
Find answers to your questions from other Dell users

                
            

            

                

                    
                



            


        

    

    

        

            

                
                    
Support Services

                
            

            

                

                    Check if your device is covered by Support Services.