From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Pavel Tide <Pavel.TIde@veeam.com>,
Rovshan Pashayev <Rovshan.Pashayev@veeam.com>
Subject: Re: [pve-devel] Strange Behavior – ZFS (and other) Storage Configuration in PVE (plain text)
Date: Tue, 02 Jul 2024 11:00:43 +0200 [thread overview]
Message-ID: <1719910612.b84jr6awdq.astroid@yuna.none> (raw)
In-Reply-To: <mailman.205.1719910148.331.pve-devel@lists.proxmox.com>
On July 2, 2024 10:48 am, Rovshan Pashayev via pve-devel wrote:
> We would like to report a strange behavior that we have encountered in Proxmox, version 8.2.2. The issue is as follows:
> We noticed that ZFS storage configuration is missing mountpoint line randomly. And workaround is manually adding missing line.
what exactly do you mean by this? the entry in /etc/pve/storage.cfg?
that one should only change if you call the corresponding API endpoint
(or CLI command). please double-check the logs that no such invocation
is happening.
if you mean something else, please clearly describe how your system is
configured and what the unexpected thing that is happening is.
> We also can see same behavior was reported in your forum:
> NFS: [SOLVED] - Proxmox 3.1 Lost Mount Point in Cluster | Proxmox Support Forum (https://forum.proxmox.com/threads/proxmox-3-1-lost-mount-point-in-cluster.16664/)
this is about a mount not working because of a misconfiguration
> ZFS: mountpoint missing after restoring a backup | Proxmox Support Forum (https://forum.proxmox.com/threads/mountpoint-missing-after-restoring-a-backup.110012/)
this is about a container mountpoint that cannot be restored unless the
restoring user is root@pam.
so two very different things, and both seem to also be something
completely different from the issue you describe, but maybe I
misunderstood that part ;)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-07-02 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 8:48 Rovshan Pashayev via pve-devel
2024-07-02 9:00 ` Fabian Grünbichler [this message]
[not found] <PH0PR14MB473575CF68BA7648A63F70BC9FDC2@PH0PR14MB4735.namprd14.prod.outlook.com>
2024-07-02 9:00 ` Fiona Ebner
2024-07-02 10:37 Rovshan Pashayev via pve-devel
[not found] <PH0PR14MB4735C14F3625AED36EA9D0589FDC2@PH0PR14MB4735.namprd14.prod.outlook.com>
2024-07-02 11:13 ` Fiona Ebner
2024-07-02 11:55 ` Rovshan Pashayev via pve-devel
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=1719910612.b84jr6awdq.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=Pavel.TIde@veeam.com \
--cc=Rovshan.Pashayev@veeam.com \
--cc=pve-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