Dashboard and storage allocation: Need help to allocate storage correctly

Hi!

After reading several discussions about storage allocation, I still can’t understand how to set proper storage allocation for my node.

Here is my problem: The remaining space in the Dashboard doesn’t match the remaining space in my system. I’m concerned that Satellites keeps sending data to the node when the disk will be completely full. If so, is there a risk of being penalized in any way?

  • The web Dashboard shows 40+GB free space:

  • While df -HT shows only ~5GB free space:

    Filesystem     Type      Size  Used Avail Use% Mounted on
    /dev/sdd1      ext4      3.0T  2.8T  5.0G 100% /mnt/storj2
    
  • fdisk -l /dev/sdd:

    Disk /dev/sdd: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
    Disk model: EFRX-68EUZN0    
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 415D8ECB-36E1-124A-959D-A6623B4FC25C
    
    Device     Start        End    Sectors  Size Type
    /dev/sdd1   2048 5860533134 5860531087  2.7T Linux filesystem
    

My configuration:

  • storage allocated in my docker-compose:
    environment:
          WALLET: "${WALLET}"
          EMAIL: "${EMAIL}"
          ADDRESS: "${ADDRESS}:28968"
          STORAGE: 2.7TB
    
  • I have not enabled dedicated-disk feature (config.yaml: storage2.monitor.dedicated-disk: false)
  • The disk is only used for storj:
    $ ls -lh /mnt/storj2
    
    total 8.0K
    drwxr-xr-x 7 jeremy jeremy 4.0K Feb  1 07:54 storj2_data
    drwxr-xr-x 2 jeremy jeremy 4.0K Sep 15  2024 storj2_identity
    

What do I do wrong?

Your node is pretty much full, you didn’t do anything wrong :+1:

Are you talking about the UI saying you have 43.33GB free, and your df saying 7.4G available? I can’t point to anything specific: but on a multi-TB disk a difference of 30’ish GB is a rounding error.

If it was me, I’d set “STORAGE: 2.6TB” just to give the filesystem some free space to deal with fragmentation - but otherwise just let it run and enjoy the sweet sweet payouts from a full disk! :money_mouth_face:

2 Likes

Thanks!

Exactly. Sorry it wasn’t clear in my original post (I edited the original post to make it clearer).

I’m just concerned that Satellites keeps sending data to the node when the disk will be completely full. If so, is there a risk of being penalized in any way?

Satellites don’t send you anything: they only suggest that your node is available or not (to paying customers who want to upload). If your node is full, customers don’t upload to you… so the satellite doesn’t think you have any new files: so it doesn’t check for any new files (like for an audit). Other than that… the Satellite is just happy for you to remain online.

I think the main downside is… that you probably could be paid more if you had more space to share. First world problems :winking_face_with_tongue:

1 Like

Nothing. The node offers some estimates of disk space used, but this estimate is biased depending on many external factors. For example, it is not possible for the node to discover the file system overhead for storing files without getting overly permissive access to your system, so it cannot take it into account.

If you need the node to leave some space for non-storage node use, adjust the allocation in the relative direction, that’s pretty much the only way.

2 Likes