Didier Spaier wrote on 1/14/21 2:02 AM:
Hi Jean-Pierre and All,
I have asked a similar question, last post in the thread:
https://sourceforge.net/p/ntfs-3g/mailman/message/37119780/
For now in the new 'auto' mode of the Slint installer I just advise
users to
shrink the last NTFS partition from Window to make from for Slint before
installing it, as written here:
http://slackware.uk/slint/x86_64/slint-14.2.1/doc/New_Installer/Doc_in_the_installer/FreeSpace
I did that because I really don't want that a user can't boot Windows
any more
after having installed Slint alongside Windows.
However, and taking in account the extra space needed in case of a
Windows
update that you mentioned, is there a way I can compute a "certainly
safe"
minimum size of the NTFS file system?
I usually configure a 64GB partition for Windows 10 and I put
all user data into another partition. Windows 10 uses about half
of it, but I have observed it may need 10GB to 20GB more space
when updating. I would recommend leaving 32GB free space
to Windows.
When resizing a fragmented partition, relocated data has to be
split into the available space in the target space. This implies
more fragmentation and more metadata to describe the
fragmented files. So I would recommend not resizing into less
than the currently used space + 10%, and you probably need
much more during Windows updates.
Note : ntfsresize with option --info returns the currently used
space. A safety margin over this has to be included in the target
size.
Jean-Pierre
Best regards,
Didier
_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
