DataHoarding_247

It's been running for about 6 hours and it looks like the error cleared itself? Ill keep an eye on it... So i guess back to my original question. Anyone else using a tmpfs ramdisk as your backblaze work folder to save nvme writes? Have you run into any issues?

Hey quick question. Is anyone using a tmpfs ramdsik drive as their temp data drive for backblaze? My goal is to save some read/writes on my cache nvme. I have it setup with scripts that dump the contents to my nvme cache drive on array stop and back to the tmfps drive when the array starts back up prior to the container launching. It seems to be working really well aside from one issue, which I'm not sure if its solvable or if i should abandon the idea all together. I get this error message: The scanner cannot open 1 directory, so a disk's file list stops there and files after it are not backed up, and bb-doctor names them bb-doctor is calling out the tmfps drive which obviosly isnt selected as a drive to backup and only used as a scratch disk: Backup health [ ok ] no stall detected [warn] 1 directory the scanner cannot open, so nothing inside them is backed up: D:\ - Windows error 2 rename the directory, or fix its ownership, and the next scan runs through. The comand im using to make the tmpfs drive is this: mount -t tmpfs -o size=6G tmpfs /mnt/disks/backblaze_ramdisk Keep in mind it is working perfectly fine as a scratch disk as far as i can tell and I dont have it selected as a drive for backups. Backblaze is able to create and flush the temp .dat files so Im not sure why its showing a read error. Maybe i need to use a different comand when creating the tmpfs folder? @rogman Is it possible to suppress this error from showing in the Backblaze64 Monitor health section. I've dismissed it within the docker but its still showing in the plugin. Thanks for any help backblaze64-diag-202610171709.zip