all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH storage v2 2/3] disks: die if storage name is already in use
Date: Fri, 19 Aug 2022 10:21:57 +0200	[thread overview]
Message-ID: <1660897234.79lpydl84s.astroid@nora.none> (raw)
In-Reply-To: <3c556291-e140-1623-6b0d-eeb2920aab30@proxmox.com>

On August 18, 2022 5:31 pm, Aaron Lauterer wrote:
> 
> 
> On 8/18/22 17:22, Aaron Lauterer wrote:
>> 
>> 
>> On 8/17/22 13:42, Fabian Grünbichler wrote:[..]
>>>> +    die "a systemd mount unit already exists: ${mountunitpath}\n" if -e 
>>>> $mountunitpath;
>>>
>>> could check if it's identical to the one we'd generate (in the spirit of
>>> patch #3 ;))
>> 
>> I looked into it, depending on how hard we want to match the mount unit, this 
>> could be a bit hard. It contains the /dev/disk/by-uuid/... path which will not 
>> be the same as it changes with each FS creation (IIUC).
> 
> The question is, if it is a good idea to have the check since there is no easy 
> way for the user to remedy the problem without doing a manual `rm 
> /etc/systemd/system/foo.mount`.

*could* be solved by having a force parameter I guess? not sure that's a 
good idea, just throwing it out there ;)

> Putting more work into improving the whole storage mgmt situation is of course 
> also something we could do.
> 
> [...]
>> 
>>>>   sub preparetree {
>>>> @@ -336,6 +340,7 @@ __PACKAGE__->register_method ({
>>>>       my $user = $rpcenv->get_user();
>>>>       my $name = $param->{name};
>>>> +    my $node = $param->{node};
>>>
>>> nit: please also change the usage further below in this API handler if
>>> you do this
>> 
>> what exactly do you mean? defining local variables for $param->{..} ones?
>> 
> 
> okay I think I got it. was confused by looking at another part of the code.
> 




  reply	other threads:[~2022-08-19  8:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 11:58 [pve-devel] [PATCH storage v2 0/3] disks: add checks, allow add_storage on other nodes Aaron Lauterer
2022-07-15 11:58 ` [pve-devel] [PATCH storage v2 1/3] diskmanage: add mounted_paths Aaron Lauterer
2022-08-17 11:35   ` Fabian Grünbichler
2022-07-15 11:58 ` [pve-devel] [PATCH storage v2 2/3] disks: die if storage name is already in use Aaron Lauterer
2022-08-17 11:42   ` Fabian Grünbichler
2022-08-18 15:22     ` Aaron Lauterer
2022-08-18 15:31       ` Aaron Lauterer
2022-08-19  8:21         ` Fabian Grünbichler [this message]
2022-08-19  9:29           ` Aaron Lauterer
2022-08-19  8:20       ` Fabian Grünbichler
2022-08-19  9:28         ` Aaron Lauterer
2022-07-15 11:58 ` [pve-devel] [PATCH storage v2 3/3] disks: allow add_storage for already configured local storage Aaron Lauterer
2022-08-17 11:53   ` 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=1660897234.79lpydl84s.astroid@nora.none \
    --to=f.gruenbichler@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