From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 818A01FF13C for ; Thu, 14 May 2026 17:25:55 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5530C37BC6; Thu, 14 May 2026 17:25:55 +0200 (CEST) From: Christian Ebner To: pbs-devel@lists.proxmox.com Subject: [PATCH proxmox-backup 5/5] fix #7533: restore-daemon: last resort fallback to mount via ntfs-3g Date: Thu, 14 May 2026 17:25:10 +0200 Message-ID: <20260514152510.2273112-6-c.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260514152510.2273112-1-c.ebner@proxmox.com> References: <20260514152510.2273112-1-c.ebner@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778772315964 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.069 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: RTIZDYYHVHZSQ7SZ5TPCCC7WO43QLN4Q X-Message-ID-Hash: RTIZDYYHVHZSQ7SZ5TPCCC7WO43QLN4Q X-MailFrom: c.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Some Windows NTFS partitions fail to mount with the current in-kernel filesystem implementations. The same filesystems can however be mounted using the user space ntfs-3g implementation. Provide a last resort fallback if all other attempts fail to mount ai disk or partition, trying to use the FUSE implementation of ntfs-3g. Fixes: https://bugzilla.proxmox.com/show_bug.cgi?id=7544 Signed-off-by: Christian Ebner --- Tested this by a modified version where the in-kernel ntfs and ntfs3 were excluded from the supported fs list. .../src/proxmox_restore_daemon/disk.rs | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/proxmox-restore-daemon/src/proxmox_restore_daemon/disk.rs b/proxmox-restore-daemon/src/proxmox_restore_daemon/disk.rs index 7936dc764..e1777d1b1 100644 --- a/proxmox-restore-daemon/src/proxmox_restore_daemon/disk.rs +++ b/proxmox-restore-daemon/src/proxmox_restore_daemon/disk.rs @@ -344,6 +344,15 @@ impl Filesystems { } } + info!("All provided in-kernel filesystems failed: try FUSE mount using ntfs-3g"); + + let mut cmd = Command::new("/usr/bin/ntfs-3g"); + cmd.args(["-o", "ro", source, target].iter()); + match run_command(cmd, None) { + Ok(_) => return Ok(()), + Err(err) => warn!("ntfs-3g mount failed for '{source}': {err:#}"), + } + bail!("all mounts failed or no supported file system") } -- 2.47.3