all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Max R. Carrara" <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-storage v1 3/3] plugin: improve error handling when creating a content subdir fails
Date: Fri,  5 Dec 2025 16:43:56 +0100	[thread overview]
Message-ID: <20251205154404.446338-4-m.carrara@proxmox.com> (raw)
In-Reply-To: <20251205154404.446338-1-m.carrara@proxmox.com>

Wrap the call to `mkpath` in an `eval` and add some additional context
to the error message, namely that creating the content directory for a
given vtype failed.

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

Do all this with the help of an anonymous subroutine, because the body
inside the loop would otherwise get a little convoluted / hard to
parse. Also, use the `/x` flag for the regexes to make them a tiny bit
easier to read.

Spotted in the community forum:
https://forum.proxmox.com/threads/bug-creating-nfs-volume-storage.177354/

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

Notes:
    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 | 25 +++++++++++++++++++++++--
 1 file changed, 23 insertions(+), 2 deletions(-)

diff --git a/src/PVE/Storage/Plugin.pm b/src/PVE/Storage/Plugin.pm
index 617b0f8..975641b 100644
--- a/src/PVE/Storage/Plugin.pm
+++ b/src/PVE/Storage/Plugin.pm
@@ -1903,6 +1903,28 @@ sub activate_storage {
         return;
     }
 
+    my $try_create_subdir = sub {
+        my ($vtype) = @_;
+
+        my $subdir = $class->get_subdir($scfg, $vtype);
+
+        eval { mkpath $subdir; };
+        if ($@) {
+            my $msg = "failed to create content directory '$subdir' for content '$vtype'";
+            my $msg_prompt = "ensure that the storage has read and write access!";
+
+            if ($@ =~ m/permission \s denied/ix) {
+                die "$msg - permission denied - $msg_prompt\n";
+            }
+
+            if ($@ =~ m/read -? only \s file \s? system/ix) {
+                die "$msg - read-only file system - $msg_prompt\n";
+            }
+
+            die "$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 +1940,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



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

      parent reply	other threads:[~2025-12-05 15:43 UTC|newest]

Thread overview: 4+ 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
2025-12-05 15:43 ` 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=20251205154404.446338-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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal