QNAP agent install on ram fs? #1702
|
Is there a reason the agent installs on the root FS which is the ram FS? Wouldn't it make more to install it in a FS that has more space and just use a symbolic link back to the root FS? I'm sure there is a reason just trying to understand why |
Replies: 3 comments 1 reply
|
It actually already works the way you're suggesting, just in reverse. The persistent copy lives on your data volume at Running from the copy keeps the agent independent of the data volume during volume maintenance. The cost is about 40 MB of RAM fs. Is space actually running tight on your model? |
|
Yeah it's putting me at 92% on the FS. I guess I don't care too much besides the fact I can't find a way to set the threshold by FS on the NAS so I need to acknowledge the alert every time I upgrade or reboot the pulse LXC. For reference it's a TS-251 which I know is running on borrowed time! It's probably about 8 years old but it does exactly what I need to do so haven't found a reason to replace it yet. |
|
You can set that per filesystem in Pulse rather than acknowledging it each time. Alerts → Thresholds has a Machine Disks section where each of the agent's filesystems gets its own row, so you can raise the Disk % for just the root fs or disable alerting on that one mount. The override is persisted, it will not come back after a reboot or agent upgrade. |
|
Thats exactly what I needed!! Thank you so much for pointing this out for me!! |
You can set that per filesystem in Pulse rather than acknowledging it each time. Alerts → Thresholds has a Machine Disks section where each of the agent's filesystems gets its own row, so you can raise the Disk % for just the root fs or disable alerting on that one mount. The override is persisted, it will not come back after a reboot or agent upgrade.
How Pulse handles triage