From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH backup v3 2/3] remove create & truncate when create_new is used
Date: Mon, 27 Jan 2025 13:27:37 +0100 [thread overview]
Message-ID: <1737980603.gjlfeg0jh5.astroid@yuna.none> (raw)
In-Reply-To: <20250127121016.247973-2-m.sandoval@proxmox.com>
this one I already applied in v2?
On January 27, 2025 1:10 pm, Maximiliano Sandoval wrote:
> As per its documentation [1]:
>
>> If .create_new(true) is set, .create() and .truncate() are ignored.
>
> This gets rid of the "file opened with `create`, but `truncate`
> behavior not defined " clippy warnings.
>
> [1] https://doc.rust-lang.org/std/fs/struct.OpenOptions.html#method.create_new
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> pbs-datastore/src/datastore.rs | 2 +-
> proxmox-backup-client/src/main.rs | 2 --
> 2 files changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/pbs-datastore/src/datastore.rs b/pbs-datastore/src/datastore.rs
> index fd3990d6..75c0c16a 100644
> --- a/pbs-datastore/src/datastore.rs
> +++ b/pbs-datastore/src/datastore.rs
> @@ -749,9 +749,9 @@ impl DataStore {
>
> let mut open_options = std::fs::OpenOptions::new();
> open_options.write(true);
> - open_options.truncate(true);
>
> if force {
> + open_options.truncate(true);
> open_options.create(true);
> } else {
> open_options.create_new(true);
> diff --git a/proxmox-backup-client/src/main.rs b/proxmox-backup-client/src/main.rs
> index 632a2917..589a097b 100644
> --- a/proxmox-backup-client/src/main.rs
> +++ b/proxmox-backup-client/src/main.rs
> @@ -1598,7 +1598,6 @@ async fn restore(
> if let Some(target) = target {
> let mut writer = std::fs::OpenOptions::new()
> .write(true)
> - .create(true)
> .create_new(true)
> .open(target)
> .map_err(|err| {
> @@ -1724,7 +1723,6 @@ async fn restore(
> let mut writer = if let Some(target) = target {
> std::fs::OpenOptions::new()
> .write(true)
> - .create(true)
> .create_new(true)
> .open(target)
> .map_err(|err| format_err!("unable to create target file {:?} - {}", target, err))?
> --
> 2.39.5
>
>
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
>
>
>
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-01-27 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 12:10 [pbs-devel] [PATCH backup v3 1/3] use truncate whenever we create files Maximiliano Sandoval
2025-01-27 12:10 ` [pbs-devel] [PATCH backup v3 2/3] remove create & truncate when create_new is used Maximiliano Sandoval
2025-01-27 12:27 ` Fabian Grünbichler [this message]
2025-01-27 12:37 ` Maximiliano Sandoval
2025-01-27 12:10 ` [pbs-devel] [PATCH backup v3 3/3] pxar: extract: Follow overwrite_flags when opening file Maximiliano Sandoval
2025-01-27 12:27 ` [pbs-devel] applied: " Fabian Grünbichler
2025-01-27 12:27 ` [pbs-devel] applied: [PATCH backup v3 1/3] use truncate whenever we create files 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=1737980603.gjlfeg0jh5.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=pbs-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