From: Rovshan Pashayev via pve-devel <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Rovshan Pashayev <Rovshan.Pashayev@veeam.com>,
Pavel Tide <Pavel.TIde@veeam.com>
Subject: [pve-devel] Strange Behavior – ZFS (and other) Storage Configuration in PVE (plain text)
Date: Tue, 2 Jul 2024 08:48:38 +0000 [thread overview]
Message-ID: <mailman.205.1719910148.331.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 12436 bytes --]
From: Rovshan Pashayev <Rovshan.Pashayev@veeam.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Pavel Tide <Pavel.TIde@veeam.com>
Subject: Strange Behavior – ZFS (and other) Storage Configuration in PVE (plain text)
Date: Tue, 2 Jul 2024 08:48:38 +0000
Message-ID: <PH0PR14MB473575CF68BA7648A63F70BC9FDC2@PH0PR14MB4735.namprd14.prod.outlook.com>
Dear Proxmox Developers,
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.
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/)
ZFS: mountpoint missing after restoring a backup | Proxmox Support Forum (https://forum.proxmox.com/threads/mountpoint-missing-after-restoring-a-backup.110012/)
We kindly request clarification on whether this behavior is expected and if you are already aware of this issue.
We are interested to know if there are plans to address and resolve this in future updates of Proxmox.
If you require any further information or clarification, please do not hesitate to ask.
Thank you for your prompt attention to this matter. I look forward to hearing from you soon.
Best Regards,
Rovshan Pashayev
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-07-02 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 8:48 Rovshan Pashayev via pve-devel [this message]
2024-07-02 9:00 ` Fabian Grünbichler
[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=mailman.205.1719910148.331.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=Pavel.TIde@veeam.com \
--cc=Rovshan.Pashayev@veeam.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