From: dea <dea@corep.it>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] Possible problem on NFS storage with release 2-3-3 (??)
Date: Wed, 15 Mar 2023 08:51:35 +0100 [thread overview]
Message-ID: <37dc5e1b-44d2-70d3-803f-d2d88b10bdcf@corep.it> (raw)
In-Reply-To: <e9f18faf-d7d1-ba40-c517-b7902a669fee@corep.it>
Hi Thomas,
what I am about to say is not related to the problem, but it has a sense
that connects it.
If it were possible during the garbage collect function to introduce
"checkpoints" so that in the case of a reboot or upgrade a days' worth
of work is not thrown away, it would really be a great step forward.
Now I use about 300 Tbytes of hybrid storage (HDD with acceleration SSD)
and about 25 Tbytes of full SSD and the garbage collect function is
really onerous on the hybrid storage.
If I were to increase the capacity to 1 Pbyte and more, it would be
really difficult to manage.
Thanks
Luca
next prev parent reply other threads:[~2023-03-15 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 8:52 dea
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 [this message]
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=37dc5e1b-44d2-70d3-803f-d2d88b10bdcf@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