public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Max R. Carrara" <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-storage v2 3/3] plugin: improve error handling when creating a content subdir fails
Date: Thu, 23 Apr 2026 11:46:16 +0200	[thread overview]
Message-ID: <20260423094619.205988-4-m.carrara@proxmox.com> (raw)
In-Reply-To: <20260423094619.205988-1-m.carrara@proxmox.com>

Replace the call to `mkpath()` with a helper inline subroutine that
uses `make_path()` instead. Follow the docs of `File::Path` [1] in
order to make our error handling here more finely-grained.

Note that the helper sub is mainly there to make the body of the loop
where `mkpath()` was originally called less convoluted / complex.

Add some additional context to the error message, namely that creating
the content directory for a given vtype failed. Also extract and
attach `make_path()`'s error message.

Handle "Permission denied" and "Read-only file system" errors
separately and, in addition to the context, tell the user to ensure
that the storage has read and write access when such errors occur.

Initially spotted this in the community forum [2].

[1]: https://perldoc.perl.org/File::Path#ERROR-HANDLING
[2]: https://forum.proxmox.com/threads/bug-creating-nfs-volume-storage.177354/

Signed-off-by: Max R. Carrara <m.carrara@proxmox.com>
---

Notes:
    NOTE: I ran into the second branch (the one for "Read-only file
    system") when testing things using my local NFS share—I figured I
    might as well handle that one too, since it's similar in nature.

 src/PVE/Storage/Plugin.pm | 30 ++++++++++++++++++++++++++++--
 1 file changed, 28 insertions(+), 2 deletions(-)

diff --git a/src/PVE/Storage/Plugin.pm b/src/PVE/Storage/Plugin.pm
index 04d87842..294a59e8 100644
--- a/src/PVE/Storage/Plugin.pm
+++ b/src/PVE/Storage/Plugin.pm
@@ -1903,6 +1903,33 @@ sub activate_storage {
         return;
     }

+    my $try_create_subdir = sub {
+        my ($vtype) = @_;
+
+        my $subdir = $class->get_subdir($scfg, $vtype);
+
+        File::Path::make_path($subdir, { error => \my $errors });
+        if (defined($errors) && scalar($errors->@*)) {
+            my $msg = "failed to create content directory '$subdir' for content '$vtype'";
+
+            for my $err_hash ($errors->@*) {
+                my ($file, $err_msg) = $err_hash->%*;
+
+                if (
+                    $err_msg =~ m/permission \s denied/ix
+                    || $err_msg =~ m/read -? only \s file \s? system/ix
+                ) {
+                    my $msg_prompt =
+                        "ensure that you have read and write access to your storage!";
+
+                    die "$msg - $err_msg - $msg_prompt\n";
+                }
+
+                die "$msg - $err_msg\n";
+            }
+        }
+    };
+
     # TODO: mkdir is basically deprecated since 8.0, but we don't warn here until 8.4 or 9.0, as we
     # only got the replacement in 8.0, so no real replacement window, and its really noisy.

@@ -1918,8 +1945,7 @@ sub activate_storage {
                 defined($scfg->{content}->{$vtype})
                 || ($vtype eq 'backup' && defined($scfg->{content}->{'rootdir'}))
             ) {
-                my $subdir = $class->get_subdir($scfg, $vtype);
-                mkpath $subdir;
+                $try_create_subdir->($vtype);
             }
         }
     }
--
2.47.3





      parent reply	other threads:[~2026-04-23  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  9:46 [PATCH pve-storage v2 0/3] Improve mkpath Error Message in activate_storage Max R. Carrara
2026-04-23  9:46 ` [PATCH pve-storage v2 1/3] plugin: use guard clause to reduce nesting Max R. Carrara
2026-04-23  9:46 ` [PATCH pve-storage v2 2/3] plugin: remove needless inequality check when creating content subdirs Max R. Carrara
2026-04-23  9:46 ` 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=20260423094619.205988-4-m.carrara@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 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