From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: superseded: [pve-devel] [PATCH pve-storage v1 0/3] Improve mkpath Error Message in activate_storage
Date: Thu, 23 Apr 2026 11:47:30 +0200 [thread overview]
Message-ID: <DI0FTRDZ3Q41.DJ139RSLNZV7@proxmox.com> (raw)
In-Reply-To: <20251205154404.446338-1-m.carrara@proxmox.com>
On Fri Dec 5, 2025 at 4:43 PM CET, Max R. Carrara wrote:
> Noticed a thread in the forum[forum] today where a user ran into the
> following error when configuring a new NFS storage:
>
> "create storage failed: mkdir /path/to/mountpoint/: Permission denied at
> /usr/share/perl5/PVE/Storage/Plugin.pm line 1919"
>
> Since it seemed that the user couldn't really interpret the error
> correctly, improve that particular part in the code and make the error
> handling / messaging a bit nicer for end users there.
>
> [...]
Superseded-by: https://lore.proxmox.com/pve-devel/20260423094619.205988-1-m.carrara@proxmox.com/T/
prev parent reply other threads:[~2026-04-23 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 15:43 [pve-devel] [PATCH pve-storage v1 0/3] Improve mkpath Error Message in activate_storage Max R. Carrara
2025-12-05 15:43 ` [pve-devel] [PATCH pve-storage v1 1/3] plugin: use guard clause to reduce nesting Max R. Carrara
2025-12-05 15:43 ` [pve-devel] [PATCH pve-storage v1 2/3] plugin: remove needless inequality check when creating content subdirs Max R. Carrara
2026-01-19 10:58 ` Fiona Ebner
2025-12-05 15:43 ` [pve-devel] [PATCH pve-storage v1 3/3] plugin: improve error handling when creating a content subdir fails Max R. Carrara
2026-01-15 14:33 ` Fabian Grünbichler
2026-04-23 9:47 ` Max R. Carrara [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=DI0FTRDZ3Q41.DJ139RSLNZV7@proxmox.com \
--to=m.carrara@proxmox.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 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.