From: Daniel Berteaud <daniel@firewall-services.com>
To: pve-user <pve-user@pve.proxmox.com>
Subject: [PVE-User] PBS : is dirty-bitmap really accurate ?
Date: Wed, 22 Jul 2020 18:40:34 +0200 (CEST) [thread overview]
Message-ID: <1110267368.76036.1595436034847.JavaMail.zimbra@fws.fr> (raw)
Hi
I've started playing with PBS on some VM. So far, it's looking really promizing.
There's one strange thing though : the percent of the dirty data. For example, I backup one VM every 2 or 3 days. It's a moderately busy server, mainly serving a MariaDB database (zabbix server + mariadb). On each backup, I get similar dirty values :
INFO: using fast incremental mode (dirty-bitmap), 492.7 GiB dirty of 590.0 GiB total
While I'm sur not even 10% of this has really been written.
Get more or less the same problem on other VM. One which I know just sleep all day (my personnal OnlyOffice document server), and which I backup daily, and get values like :
INFO: using fast incremental mode (dirty-bitmap), 5.0 GiB dirty of 10.0 GiB total
Or another small one (personnal samba DC controler) :
INFO: using fast incremental mode (dirty-bitmap), 13.0 GiB dirty of 20.0 GiB total
The only write activity for those 2 are just a few KB or maybe MB of log lines. Respectivly 5 and 13GB of dirty blocks seems unreal.
Am I the only one seeing this ? Could the dirty-bitmap mark dirty blocks without write activity somehow ?
Regards,
Daniel
--
[ https://www.firewall-services.com/ ]
Daniel Berteaud
FIREWALL-SERVICES SAS, La sécurité des réseaux
Société de Services en Logiciels Libres
Tél : +33.5 56 64 15 32
Matrix: @dani:fws.fr
[ https://www.firewall-services.com/ | https://www.firewall-services.com ]
next reply other threads:[~2020-07-22 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 16:40 Daniel Berteaud [this message]
2020-07-23 6:43 ` Fabian Grünbichler
2020-07-23 6:53 ` Daniel Berteaud
2020-07-23 9:00 ` Jorge Boncompte
2020-07-23 9:34 ` Fabian Grünbichler
2020-07-23 9:40 ` Daniel Berteaud
2020-07-23 21:59 ` Roland
2020-07-24 7:02 ` Daniel Berteaud
2020-07-24 7:54 ` Ronny Aasen
2020-07-26 9:24 ` Mark Schouten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1110267368.76036.1595436034847.JavaMail.zimbra@fws.fr \
--to=daniel@firewall-services.com \
--cc=pve-user@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox