search
HomepageBlog

Cache Configuration Requirements

To successfully implement the Cache Configuration, the system must support two primary features:

  1. Data Archiving

  2. Scan LTFS Tape

The caching system should function as a block device accessible via the /dev/ directory, or any supported mounted filesystem. Possible configurations include:

  • Internal RAID on local disks

  • Internal RAID on JBOD setups

  • SCSI Attached Storage

  • iSCSI Attached Storage

  • Linux-based block replication (e.g., DRBD, GlusterFS)

hashtag
Cache configuration

To proceed when the cache disk is unready, initialize it by running these commands.

To set up the CACHE Disk, follow these steps:

  1. Create the CACHE Disk:

circle-info

Replace sdX with the correct device identifier, likely sdb.

  1. Select the CACHE Disk:

circle-info

Use the same device identifier as in the previous step.

The process will then begin.

After configuration, the disk functions as a cache. You can then check its status.

hashtag
Extend your cache

To enhance the cache size, adjust the solution according to the server type.

circle-exclamation

Backup Your Data: Before extending the cache, ensure all cache data is copied to secondary storage.

hashtag
Increasing Disk Volume Capacity

RAID

  1. Add New Disk(s): Introduce new disk(s) to the existing RAID volume serving as Nodeum Cache.

  2. Wait for RAID Reconstruction: Allow time for the RAID reconstruction to complete, which may take several days depending on the disk size.

Virtual Machine Datastore

  1. Shutdown the Nodeum Server: Ensure the Nodeum server is safely shut down.

  2. Edit Server Settings: Adjust the Nodeum server settings by selecting the appropriate disk and expanding its size.

  3. Save Configurations: Apply and save the new configurations.

hashtag
Extend the volume partition

circle-exclamation

When creating a new disk partition larger than 16TB, the resize2fs command (version <1.43) will fail with the error: "resize2fs: New size too large to be expressed in 32 bits". To resolve this, use the latest version of Gparted, which supports the 64-bit version of this command. Below is a guide on how to use Gparted.

hashtag
Using GParted Live ISO to Graphically Edit Disk Size

  1. Download the GParted ISO:

  2. Create a Bootable USB:

  3. Boot from Live ISO:

    • For Physical Servers: Use a CD/USB or a Remote Management Server interface to boot.

    • For Virtual Servers: Boot the VM using the downloaded GParted ISO.

  4. Resize Partition Graphically:

    • After booting, you will see the GParted graphical interface.

    • Note: For disks larger than 16 TB, ensure a 64-bit file system. Convert using:

    • Select your Nodeum cache disk (typically /dev/sdb1).

    • Click 'Resize/Move'.

    • Drag the vertical bar to adjust partition size.

    • Click 'Resize/Move' again.

    • Apply changes.

  5. Finish Up:

    • Reboot the server to utilize the new, larger cache size.

hashtag
Command Line Interface Procedure

  • Stopping the Nodeum services

  • Identify the disk mounted at /mnt/CACHE to determine if it needs to be expanded.

  • Umount the Cache disk

  • Check the disk

Ensure functionality works correctly; stop to address any unfixed errors before proceeding.

  • use parted to extend the partition size

  • Check the disk again

  • Extend the disk size

circle-exclamation

If the operation fails, refer to Cautions 1 above.

  • Mount the disk

  • Start the Nodeum services

Last updated

Was this helpful?