Rich W wrote:
Hi there,
I'm currently evaluating fsarchiver. When using it to back up a Windows
10 system partition, there's a lot of errors within its output due
to lgetxattr returning ELINK. This prevents the file from being included
within the backup archive.
AFAIK, fsarchiver is about saving files, and this makes it difficult
to get file parameters from a file system whose parameters do not
fit into Posix concepts.
The ELINK issue is about associating a short name to the correct
long name when the file has several long names.
A secondary issue with short names is that Windows creates them
automatically, inserting some number so that there is no name
conflict. When restoring, the same name has to be restored, but
it may have already been associated to another file.
There's been some discussion regarding it in the following thread to
which developer Jean-Pierre mentioned a possible workaround for the issue.
https://tuxera.com/forum/viewtopic.php?p=37908&sid=8628e81f35ab27c7379d89aabe3a4193#p37908
This was in 2013 before Windows 10 came out.
I would like to implement this in fsarchiver if possible, and get it
merged into its primary tree. Can he please advise of the details of
this workaround?
The solutions I had in mind were not implemented, as I did not
have a candidate to test them. Wimlib could however create an
archive by linking to libntfs-3g instead of using the standard
Posix functions.
With Windows 10 (and particularly its system partition) new
issues arise, such as dealing with system-compressed files
(how to read or write them without decompressing), EAs (which
contain unknown integrity checks), multiple logged-utility-streams
(not supported by ntfs-3g), references to cloud files, etc.
IMHO saving files is not the right way to backup a system
partition. Saving the full partition is a better way.
Jean-Pierre
Thanks,
Rich.
_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
