goldcoin93

Thanks again. Not sure if I understand this. Minimum free space is what UnRaid will be the minimum space in the drive before rejecting any write into the drive. In other words, if I have minimum free space set as 300Gb, technically, I can only use 700Gb in a 1TB drive, correct?

Thanks. That's something I didn't set. I let UnRaid set it since at that time, I didn't know I was going to fill my 12 TB so fast. I don't have anything larger than 400Gb. I lowered it to 100Gb and everything went back to normal. I'm adding 14 TB tomorrow so I'll pump it back. Not sure what's usually the best practice for this. Any advise?

Hello, I noticed that one of my containers reported that were "no space left on device" and when I try to copy a file from the cache drive over to a folder in the array, I get the error below (using Dynamix File Manager for the move). I am wondering if there is something allocating space that even rsync is seeing it as no space. I am just not sure how to check for these types of allocations if any. "rsync: [receiver] mkstemp "/mnt/user/data/misc/.qbittorrent.log.bak.Bf89RB" failed: No space left on device (28) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1336) [sender=3.2.7]" dataeater-diagnostics-20240107-1712.zip

It actually increased drastically after it passed the 4TB. It is now going at 250 Mbps. Thanks!

Earlier today, I replaced my 4TB WD Red parity drive for an 18TB Exos X20. I would have expect that the parity check would go faster than before, but it seems that it is going slower. I am currently getting between 50-80 Mbps whereas before I would get 100+ Mbps. I read in another post that Disk Speed docker needed to be provided but I am not sure if I ran it correctly. I am also attaching diagnostics while the parity is running. dataeater-diagnostics-20240106-2228.zip