From: dea <dea@corep.it>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] Possible problem on NFS storage with release 2-3-3 (??)
Date: Thu, 9 Mar 2023 09:52:02 +0100 [thread overview]
Message-ID: <7ab47597-6ed5-f577-49b5-c011b67ad1a8@corep.it> (raw)
Hello everyone,
I've been using PBS on NFS storage (on several installations) for some
time now, and I'm used to some kind of performance.
For example, a full SSD datastore (on the NFS datastore) I know takes 2
hours for a full garbage collect, etc. (datastore from 25 to 300 Tbytes).
This was always the case until release 2.3-2.
After the upgrade to 2.3-3 something changed (ok also to kernel 5.15-85)
the same datastore that used to be completed in 2 hours, now after 3
days is 95% in marked mode.
Something does not add up for me (datastore side has not been touched a
comma), ditto for PBS configuration.
The PBS is in production, as soon as I can I would like to upgrade it to
kernel 6.1 .... I don't know what could be the cause.
I don't understand.....
Many thanks
Luca
next reply other threads:[~2023-03-09 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 8:52 dea [this message]
2023-03-09 12:38 ` dea
2023-03-14 8:20 ` Thomas Lamprecht
2023-03-14 8:45 ` dea
2023-03-15 7:51 ` dea
2023-04-13 14:16 ` dea
2023-03-14 12:30 ` dea
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=7ab47597-6ed5-f577-49b5-c011b67ad1a8@corep.it \
--to=dea@corep.it \
--cc=pbs-devel@lists.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