From: "Daniel Koch" <koch@triple6.org>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] PBS File Retore for NTFS with deduplication enabled leads to corrupted files
Date: Tue, 19 Apr 2022 09:11:32 +0000 [thread overview]
Message-ID: <1b2352293236d294d999512314a9d06e@triple6.org> (raw)
Hello List,
Current situation:
Using PBS for NTFS with the de-duplication feature enabled (https://docs.microsoft.com/en-us/windows-server/storage/data-deduplication/overview) results in
corrupted file restores.
ntfs3 can't handle de-duplicated file systems atm.
ntfs-3g by default is not aware of ntfs'es de-duplication but provides plugins for those features:
https://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g-old.html#download
Is there any chance that the restore kernel will use ntfs-3g over ntfs3 with dedup capabilities? The de-duplication feature of NTFS is widely used and people don't seam to be aware that their backups are actually corrupted.
Restoring the whole disk image will be fine tho.
Kind regards,
Daniel
next reply other threads:[~2022-04-19 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 9:11 Daniel Koch [this message]
2022-04-22 10:04 Dietmar Maurer
2022-04-22 10:54 ` Roland Sturm
2022-04-27 4:30 Dietmar Maurer
2022-04-27 7:35 ` Fabian Grünbichler
2022-04-27 12:16 ` Thomas Lamprecht
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=1b2352293236d294d999512314a9d06e@triple6.org \
--to=koch@triple6.org \
--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