ECS: xDoctor: RAP007: Symptom Code: 2028: spazio su disco insufficiente per il file system root (in inglese)

Riepilogo: ECS: xDoctor: RAP007: SymptomCode: 2028: spazio su disco insufficiente per il file system root (in inglese)

Questo articolo si applica a Questo articolo non si applica a Questo articolo non è legato a un prodotto specifico. Non tutte le versioni del prodotto sono identificate in questo articolo.
Scopri le altre risorse

Sintomi

A partire da ECS xDoctor v4.8-108.0 e ObjectScale xDoctor v5.1-108.0, RAP007 (LVRoot troppo pieno) viene implementato come strumento di guarigione automatica. Quando il file system root supera la soglia di errore o critico , xDoctor genera un avviso RAP007 e richiama automaticamente il processo di orchestrazione delle riparazioni integrato per eseguire la pulizia necessaria (quando i guaritori automatici xDoctor sono abilitati).

 

Nota:  Se la distribuzione esegue una versione di xDoctor inferiore alla 108, lo strumento di guarigione automatica non è disponibile. È necessario utilizzare il processo di pilota automatico descritto di seguito o eseguire la procedura di correzione manuale fornita nella sezione relativa alla risoluzione.

 

Avviso che attiva la correzione automatica RAP007

Questo avviso viene generato nel momento in cui l'utilizzo del file system root supera la soglia di gravità ed è ciò che avvia il flusso di lavoro dell'auto-healer.

RAP007: Root del file system (/)(RFS) spazio su disco insufficiente

  • LVRoot troppo pieno
  • Una delle risorse RFS ha superato una determinata soglia di gravità.
  • RAP007
  • RAP 007
  • SymptomCode: 2028

Esempio di output di avviso: 

Nota: Tutte le versioni precedenti a ECS xDoctor v4.8-108.0 e ObjectScale xDoctor v5.1-108.0 avvisano solo di questo problema.

------------------------------------------------------
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

  

  
Correzione di AutoHealer (esempio)

  
Quando i guaritori automatici sono abilitati, xDoctor tenta la pulizia immediata e segnala lo spazio recuperato.

  

  

  
---------------------------------------------
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."}}

  



  
Requisito del guaritore automatico

  
I guaritori automatici devono essere abilitati durante l'installazione o dopo l'installazione utilizzando KB: ECS: xDoctor: Come abilitare xDoctor Auto Healer dopo l'installazione dello strumento

  
 

  
Passaggi di convalida manuale:

  
Esaminare l'output del nodo interessato:

  

   Comando:
   
df -k /

   
Esempio:
  

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


  


   Confermare questo output del comando del nodo interessato in formato leggibile:

  

   Comando:
   
df -h /

   
Esempio:
  

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


  



   Verificare che la dimensione RFS sugli altri nodi sia inferiore all'80%.

  

   Comando:
   
svc_exec "df -h | grep LVRoot"

   
Esempio:
  

  
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% /


        
Causa

        
    
   
  • È stata aperta una Service Request attiva per questo problema.
    • 
   
  • 
    
    
     Diversi fattori possono contribuire a questa condizione, tra cui file temporanei di grandi dimensioni lasciati durante le azioni di manutenzione o supporto precedenti che ora potrebbero richiedere la pulizia.
    
    • 
  

        
Risoluzione

        
Guaritore automatico xDoctor:  ObjectScale xDoctor v5.1-108.0 / ECS xDoctor v4.8-108.0 o versioni successive

  
 

  

   
    
    
  1. Per attivare manualmente il guaritore automatico abilitato, eseguire il seguente comando sul master.rack Nodo. In questo modo vengono avviati gli analizzatori rack, che convalideranno e correggeranno automaticamente i nodi uno alla volta.
    2. 
   

  

  

   Comando:

  

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

  
Esempio:

  
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. Esegui il report della sessione per esaminare i risultati dell'esecuzione di correzione automatica manuale.
    2. 
   

  

  

   

    Comando: 
   

   

    Nota: Utilizzare il comando Report sessione fornito nell'esempio xDoctor riportato sopra per esaminare i risultati dell'esecuzione della correzione automatica manuale.
   

  

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

  
Esempio:

  
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


  

    
  

  
Pilota automatico xDoctor:

  
Questa knowledge base (KB) è ora automatizzata con xDoctor Auto Pilot e risolve la maggior parte dei problemi senza la necessità di coinvolgere l'assistenza.


   Questa funzione è nativa per xDoctor 4-8.104.0 e versioni successive; per problemi di sintassi e utilizzo, fare riferimento a ECS: ObjectScale: Come eseguire gli script di automazione della KB (pilota automatico).


   Per trovare il nodo master del rack:

  
  Comando:

  
ssh master.rack

  
Per trovare l'IP NAN, utilizzare l'IP identificato nell'avviso o dal comando riportato di seguito:

  
getrackinfo

  
 Esempio:

  
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. Eseguire il comando di automazione da un nodo primario con xDoctor 4-8.104.0 e versioni successive.
    2. 
  

  

   Comando: 
  

  

               Nota: per questa azione è supportato solo il nodo --target.
  

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

  

Esempio:

  
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. 
    
    
     Esaminare e confermare le azioni che verranno eseguite e, facoltativamente, visualizzare l'elenco dei file che verranno eliminati prima di procedere.
    
    2. 
  

  

   Comando:
   
# yes or no
   
Esempio di richiesta di conferma:
  

  
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
════════════════════════════════════════════════════════════════════════════════
: 


  

   Esempio di prompt opzionale per l'elenco dei file:
  

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


  
 

  

   Esempio di elenco di file opzionale:
  

  
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ 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. Confermare l'eliminazione dei file elencati in precedenza:
    2. 
  

  
Comando:

  
# yes or no

  
Esempio:

  
════════════════════════════════════════════════════════════════════════════════
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. Rivedere il riepilogo dei file eliminati e dei risparmi RFS derivanti dall'esecuzione:
    2. 
  

  
Esempio:

  
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ 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.
└─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────



            


        

        
        
Prodotti interessati

        ECS Appliance
    
Prodotti

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







                        

                            

    

        

            

                
                    
 Proprietà dell'articolo

                
            

            

                

                        
Numero articolo: 000079798

                

                
                

                        
Tipo di articolo: Solution

                

                

                        
Ultima modifica: 05 feb 2026


                

                    

                            
Versione:  18

                    


            


        

    

    

        

            

                
                    
Trova risposta alle tue domande dagli altri utenti Dell

                
            

            

                

                    
                



            


        

    

    

        

            

                
                    
Support Services

                
            

            

                

                    Verifica che il dispositivo sia coperto dai Servizi di supporto.