public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Rovshan Pashayev <Rovshan.Pashayev@veeam.com>,
	"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Pavel Tide <Pavel.TIde@veeam.com>
Subject: Re: [pve-devel]  Strange Behavior – ZFS (and other) Storage Configuration in PVE (plain text)
Date: Tue, 2 Jul 2024 11:00:53 +0200	[thread overview]
Message-ID: <63f31b03-a054-40fc-9d7c-dca803852813@proxmox.com> (raw)
In-Reply-To: <PH0PR14MB473575CF68BA7648A63F70BC9FDC2@PH0PR14MB4735.namprd14.prod.outlook.com>

Hi,

Am 02.07.24 um 10:48 schrieb Rovshan Pashayev:
> 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.

does the option get lost for already existing storages or does it affect
newly added ones? How do you edit/add the ZFS storages, via GUI or CLI,
please share the exact commands in the latter case. Please also note
that the storage configuration 'mountpoint' is optional. If it is not
set, it will be assumed to be the default mount point, i.e. the 'pool'
configuration option prepended by '/'.

>  
> 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/)

I don't see how this is related. There is no 'mountpoint' storage config
option for NFS storages, just a 'path'. The issue here seems to have
been wrong mount options.

> ZFS: mountpoint missing after restoring a backup | Proxmox Support Forum (https://forum.proxmox.com/threads/mountpoint-missing-after-restoring-a-backup.110012/)

The issue here is about a missing container mount point volume after
restoring a backup (which Fabian pointed out is not restored for
unprivileged users). So again, I don't see how this is related.

>  
> 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
> 

Best Regards,
Fiona


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

       reply	other threads:[~2024-07-02  9:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH0PR14MB473575CF68BA7648A63F70BC9FDC2@PH0PR14MB4735.namprd14.prod.outlook.com>
2024-07-02  9:00 ` Fiona Ebner [this message]
     [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
2024-07-02 10:37 Rovshan Pashayev via pve-devel
  -- strict thread matches above, loose matches on Subject: below --
2024-07-02  8:48 Rovshan Pashayev via pve-devel
2024-07-02  9:00 ` Fabian Grünbichler

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=63f31b03-a054-40fc-9d7c-dca803852813@proxmox.com \
    --to=f.ebner@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal