KB 754061 - BeeGFS Metadata Check Before Large File Ingest

KB 754061 - BeeGFS Metadata Check Before Large File Ingest

1. Purpose

To validate metadata and inode capacity before ingesting a very large number of small files into a BeeGFS filesystem.


Step 1 - Check Metadata Inodes

Run beegfs-df on any BeeGFS client
This checks if the nodes have enough Inode capacity for ingesting large number of files and this command will also shows the available capacity for both Storage and Metadata targets.

For example:

beegfs-df


Quote

METADATA SERVERS:

TargetID   Cap. Pool        Total         Free    %      ITotal       IFree    %

========   =========        =====         ====    =      ======       =====    =

     101      normal    5093.9GiB    5093.7GiB 100%     3561.9M     3561.9M 100%

     201      normal    5093.9GiB    5093.7GiB 100%     3561.9M     3561.9M 100%

     301      normal    5093.9GiB    5093.7GiB 100%     3561.9M     3561.9M 100%

     401      normal    5093.9GiB    5093.7GiB 100%     3561.9M     3561.9M 100%

     501      normal    5093.9GiB    5093.7GiB 100%     3561.9M     3561.9M 100%

     601      normal    5093.9GiB    5093.7GiB 100%     3561.9M     3561.9M 100%

     701      normal    5093.9GiB    5093.7GiB 100%     3561.9M     3561.9M 100%

     801      normal    5093.9GiB    5093.7GiB 100%     3561.9M     3561.9M 100%

STORAGE TARGETS:

TargetID   Cap. Pool        Total         Free    %      ITotal       IFree    %

========   =========        =====         ====    =      ======       =====    =

     101      normal   13728.8GiB   13633.0GiB  99%     1439.8M     1439.8M 100%

     102      normal   13728.8GiB   13633.0GiB  99%     1439.8M     1439.8M 100%

The IFree column shows the Inodes available in each metadata target
​


Step 2. Check Client Mount

Run df -i /mnt/beegfs to confirm the mount is healthy and not inode-constrained.


Step 3 - Identify Metadata Target for Ingest Directory

Run beegfs-ctl --getentryinfo </path/to/ingest/directory> to check what metadata server is attributed to their directory
Note the metadata target ID and all files created under this directory will hit the same metadata server.

For example:

Quote

# beegfs-ctl --getentryinfo /mnt/beegfs/

Entry type: directory

EntryID: root

Metadata node: meta_06_tgt_0601 [ID: 601]

Stripe pattern details:

+ Type: RAID0

+ Chunksize: 512K

+ Number of storage targets: desired: 4

+ Storage Pool: 1 (Default


Step 4 - Validation Checklist

Before proceeding with the ingest, confirm:

  • Metadata targets show sufficient IFree

  • BeeGFS client mount has available inodes

  • Ingest directories are spread across metadata servers

  • Expected file count is documented

    • Recent Articles

    • KB-630208 | How to use Find and Locate to search for files in Linux

      Purpose To provide Linux administrators and Field Engineers with guidance on using the find and locate utilities to efficiently search for files and directories within a Linux filesystem based on criteria such as name, type, size, timestamps, ...

    • KB-630164 | How to use rsync to Synchronize Files

      Purpose To provide a clear and practical procedure for using the rsync utility to synchronize files and directories between local systems and remote hosts, including push and pull operations, while preserving file attributes and optimizing data ...

    • KB-630107 | How to create a Linux swap file

      Purpose To provide Field Engineers and Linux administrators with a standardized procedure for creating, configuring, and validating a Linux swap file. This procedure helps ensure sufficient virtual memory is available when physical RAM is exhausted ...

    • MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims

      MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims MSI's standard warranty does not cover physical or accidental damage to an All-in-One (AIO) PC. If the damage is determined to be caused by external factors rather than a ...

    • KB 134833 - Troubleshooting NVSM Alert NV-CPU-XX – Unrecoverable CPU Internal Error

      Purpose This document provides a general troubleshooting procedure for the NVIDIA System Management (NVSM) alert NV-CPU-XX, which indicates that a CPU has reported an internal error. The article outlines how to verify whether the alert represents an ...

    • Popular Articles

    • CP Plus Camera and NVR Configuration

      NVR Configuration The CP Plus Pro Series of NVRs have been meticulously designed for providing you with upgraded performance and higher recording quality in your IP video surveillance solution. The robust processor that has been inculcated in this ...

    • KB 775235 - Kerberos Authentication – Overview

      What is Kerberos? Kerberos is a secure authentication method used in our Active Directory (AD) environment (mbuzztech.com). It allows users to: Access multiple systems without re-entering passwords (Single Sign-On – SSO) Log in once Where We Use It ...

    • How to Remove and Reinstall NVIDIA Drivers on Ubuntu

      This article provides step by step guide to completely remove existing NVIDIA drivers and reinstall specific version of the NVIDIA driver on the Ubuntu system Prerequisites Administrative (sudo) access to the Ubuntu system. Internet access to ...

    • KB 692001 - Personal Computers and Servers - Classification and Point of Contact

      We can classify the computers that MBUZZ handles based on their form-factor as below: Tower Workstations, Desktops, Gaming PCs and SFF (Small form factor) PCs fall under this category. These are computers people would use on a desk and rarely move. ...

    • KB 298031 - M.2 SSD Tier List

      The sequential read and write speeds, which are usually the most advertised number, are not a proper benchmark of real-world performance or the quality of an SSD. This article categorizes and tiers SSDs based on factors like the type of NAND flash, ...