Re: Openvz7 ploop FS + snapshots = BLOAT [message #53857 is a reply to message #53854] |
Thu, 30 May 2024 20:29 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
wsap
Messages: 70 Registered: March 2018 Location: Halifax, NS
|
Member |
|
|
nathan.brownrice wrote on Fri, 17 May 2024 13:22They are live snapshots, and to be honest I haven't tested with offline snapshots. Maybe worth a shot, but we have so many live containers we can't have downtime on them even overnight it would be sloppy.
Oh! To clarify, my understanding is that the --skip-suspend option shouldn't result in any downtime. It is supposed to *only* snapshot the disk, and not also the live memory contents. The idea being that if you restore a snapshot that has those memory contents (which they do by default), the container will resume *exactly* as it was (memory state included), whereas with --skip-suspend the disk will still be exactly as it was, but when the container comes online it'll be a fresh boot with clean memory contents.
No clue if that is contributing to your storage issue, but it's the only idea I've got left
|
|
|