Stale mount path | Community (2024)

@0ber0n, looking at the docs, which of these scenarios applies to you?

Can you browse into the mount point on the client itself?

How are the stale NFS mount points detected during the scan phase?

The stale NFS mount points are detected during the scan phase and an event notification is generated for the user to take necessary action. Stale mount points are detected by using the ls –d command. If the command takes more than 60 seconds to return output, then it is a stale mount point.

Stale NFS mount points are handled in the following ways:

• If the scan content itself is a stale mount point, then an event notification is generated for the user to take necessary action. The scan phase does not proceed for that file or directory.

• If a directory in the scan content is a stale mount point, then an event notification is generated for the user to take necessary action, but the scan phase proceeds with the rest of the scan content.

  For example, /TestFolder is the scan content, and /TestFolder/nfs_mount is one of the directories under it which is a stale mount point. The scan phase proceeds with the rest of the files and directories, ignoring the /TestFolder/nfs_mount directory.

• If the scan content is part of a parent directory that is a stale mount point, then an event notification is generated for the user to take necessary action. The scan phase does not proceed for that file or directory.

  For example, the /TestFolder/abc directory is the scan content, and /TestFolder is a stale mount point, then an event notification is generated for the user to take necessary action. The scan phase does not proceed.

Hi Mike,

Yes i can browse into the mount point on the client.

Hi @0ber0n

What does the ouput of “mount” command show? Is /data mounted correctly? Are you able to stat & create new files and folders on this mount point?

Thanks,

Sparsh

Hi @SparshGupta

Yes able to create/delete/ files and folder on this mount point.

I can share below info

>******]~#mount -l|grep -i data
/dev/mapper/datavg-lv_data on /data type xfs (rw,relatime,attr2,inode64,noquota)

Hey@0ber0n

What’s the subclient content? Is this issue being hit for all backup jobs? Could you please share FileScan.log?

Do you have multiple subclients in backupset?

Thanks,

Sparsh

Hi @SparshGupta

This is the default subclient, content is “/” and only this subclient we have.

I just saw this only 2 server yet. Filescan log attached.

Hi@0ber0n

152851 25513 09/22 01:00:34 15355770 MountPathInfo::expandContentPathByVolumes(274) - Mount '/data' of type yxfs] is a stale/filtered mount point

FileScan.log -

152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/sw]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/swdepot]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/tmp]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/log/audit]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/spool/mail]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/tmp]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter i]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/sw]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/swdepot]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/tmp]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/log/audit]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/log/lastlog]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/spool/mail]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/tmp]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter i]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/**/*.dbf]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/sw]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/swdepot]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/tmp]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/log/audit]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/log/lastlog]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/spool/mail]152851 25513 09/22 01:00:33 15355770 CSubclientContentUnix::ParseFilters(556) - parsing filter [/var/tmp]

Thanks,

Sparsh

Hi @SparshGupta

I check this on the Client, Client Computer Groups, Subclient Policy and the Global Filters but could not see any empty filter.

@0ber0n

Can you please open a case with commvault support, upload the CSDB (support team will assist with this)and share the ticket number?

Thanks,

Sparsh

Hi @0ber0n

We are working on getting the CSDB up at the moment. It might take some time.

Thanks,

Sparsh

hi @SparshGupta

I shared the outputs in the case.

Best Regards.