Data domain file system (DDFS) may restart with segfault  or panic with malloc error during data-movement to Cloud Tier
This issue is applicable to all DDOS 7.7.0.x releases and fix is included in DDOS 7.7.1.0 and later versions

Following alert will be issues during DDFS restart
Alerts History
--------------
Id      Post Time                  Clear Time                 Severity   Class        Object   Message
-----   ------------------------   ------------------------   --------   ----------   ------   -------------------------------------------------------------------------
m0-43   Thu Feb  3 05:18:43 2022   Thu Feb  3 05:19:02 2022   ERROR      Filesystem            EVT-FILESYS-00008: Filesystem has encountered an error and is restarting.
-----   ------------------------   ------------------------   --------   ----------   ------   -------------------------------------------------------------------------
There is 1 historic alert.

System will report either of followings message if DDFS restarts with segfault  error
segfault at xxxx ip yyyy sp zzzz error 4(E4) in libcrypto.so.1.0.0[7f26e22a0000+2a2000](E4)
segfault at xxxx ip yyyy sp zzzz error 4(E4) in libc-2.17.so[7f2780bee000+1b5000](E4)
segfault at xxxx ip yyyy sp zzzz error 4(E4) in ddfs[400000+4e24000](E4)

System will report either of following message and ALERT  if DDFS restarts with PANIC  error
PANIC: lib/dd_memstats.c: dd_malloc_verify_fence: 493: !(footer->magic == MALLOC_TAIL_MAGIC)
PANIC: lib/../include/dlist.h: _dl_first: 828: !(list->count != 0)

Dell Technologies has identified code defect in cloud data-movement function which will result in DDFS restart either with above SEGFAULT or PANIC error .

Jira reference is DDOSCFD-9678

To avoid DDFS restarts during cloud tier data movement, consider upgrading to DDOS 7.7.1.10 or later, 7.7.2.0.10 or later, 7.8.0.20 or later

Steps:

1. Suspend cloud data-movement process
      # data-movement stop
      # data-movement status
              
2. Restart file system
               # filesys restart
     
3. Ensure file system is enabled
               #filesys status
              
4. Upgrade system to DDOS 7.7.1.10 or later, 7.7.2.0.10 or later, 7.8.0.20 or later.
5. Resume cloud data-movement process
               # data-movement start