Jump to content

IamSpartacus

Members
  • Content Count

    655
  • Joined

  • Last visited

Community Reputation

15 Good

About IamSpartacus

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    NY

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Has anyone successfully gotten the inputs.nvidia_smi plugin working in telegraf? Even with the --runtime=nvidia extra paramater and the NVIDIA_DRIVER_CAPABILITIES/NVIDIA_VISIBLE_DEVICES variables I can not get it to work. I just get: Yet inside the container I can see nvidia-smi in /usr/bin. EDIT: Turned out to be the alpine repo. Changed to latest and now it works.
  2. Yes inside telegraf. But when I run 'which nvidia-smi' inside the container it returns /usr/bin/nvidia-smi and I see it there when I cd to /usr/bin/ inside the container as well.
  3. Has anyone successfully gotten telegraf working with inputs.nvidia-smi? Even adding all the nvidia variables to the container I still get the following error in my telegraf logs:
  4. I've created a bug report so Limetech can hopefully address this issue.
  5. Please see this thread for more information. I've seen the same behavior since 6.6 and now on to 6.7. Also with 2 completely different servers (completely different hardware).
  6. Ok so even trying to do multiple scatter jobs doesn't seem to work. The behavior you describe above is not happening. No matter what, the data is getting moved to disk8 even though it does not have the most free space. So I'm not sure if I'm doing something wrong or if Unbalance will just always start with the first chosen disk regardless of free space available.
  7. I see. So if i wanted to move 7.5TB off one drive and scatter it across 8 new drives, I'd have to select subfolders and do a different move job for each subfolder?
  8. I'm trying to do a scatter by moving a directory on disk1 to multiple disks (disks8-15, all empty). However, when I start the move it only moves the files to the first disk (disk8) in the group of disks I'm trying to move the data to. What am I missing?
  9. It's not Plex that causes high CPU, RAM, or Disk I/O. It's the mover process. I have mitigated this for the time being by scheduling my mover to only run once a day at 5am. But now that I've moved into doing a lot of 4K, sometimes i need to manually run the mover during the day and I have to hope no one is using Plex.
  10. Good thought but in my testing this was not the case. Yes Plex scans on library changes but with all the resources I have at my disposal the scan is done in less than 30 seconds. The issue seems to be CPU IOWait. Watching netdata during the mover process IOwait jumps up significantly and I don't understand why.
  11. I leave my server on 24/7 but I'd still like this feature. Sometimes I need to reboot my server while in the middle of a parity check and I have to cancel the parity check.
  12. Any acknowledgement on this? I'm not quite sure how this is not a bug but regardless this is something that should be at least "implemented" in the next minor release.
  13. How does one get 3rd Party Plugin settings (ie. CopyCompleted) to be persistent through restarts?
  14. I assume there is an easy answer on this but me being fairly noob at Linux hopefully someone can explain it to me. Looking at the used space of my disks in the WebGUI the numbers do not match up if I do a du -sh on the directory (ie. /mnt/disk1). Is the GUI calculating the space differently than the CLI?