From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Stefan Sterz <s.sterz@proxmox.com>,
Wolfgang Bumiller <w.bumiller@proxmox.com>
Cc: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] fix #3336: api: remove backup group if the last snapshot is removed
Date: Mon, 14 Mar 2022 18:12:02 +0100 [thread overview]
Message-ID: <3ef093e4-200a-efa0-2666-63fad58b0d67@proxmox.com> (raw)
In-Reply-To: <915cbd4b-a195-5714-501c-41932b2c2558@proxmox.com>
On 14.03.22 16:19, Stefan Sterz wrote:
> agreed, would you mind if i open a bug for overhauling the locking
> mechanism and started work on that? i looked a bit into your proposed
that's fine.
> solution regarding tmpfs afaict there is no per directory inode limit,
> only an overall limit corresponding to halve the physical memory
> pages. we could use a completely flat structure based on either
> encoded or hashed canonical paths. im assuming thats pretty close to
> what you had in mind?
Yeah, I'd use proxmox_sys::systemd::escape_unit for flattening lock paths
and ship a systemd .mount unit file setting up a separate tmpfs in a place
like /run/proxmox-backup/locks with a relatively high inode count (size
can/should? be relatively low)
prev parent reply other threads:[~2022-03-14 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 13:50 Stefan Sterz
2022-03-11 12:20 ` Thomas Lamprecht
2022-03-14 9:36 ` Wolfgang Bumiller
2022-03-14 10:19 ` Thomas Lamprecht
2022-03-14 11:13 ` Stefan Sterz
2022-03-14 11:36 ` Thomas Lamprecht
2022-03-14 14:18 ` Stefan Sterz
2022-03-14 14:53 ` Thomas Lamprecht
2022-03-14 15:19 ` Stefan Sterz
2022-03-14 17:12 ` Thomas Lamprecht [this message]
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=3ef093e4-200a-efa0-2666-63fad58b0d67@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.sterz@proxmox.com \
--cc=w.bumiller@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.