Hi,
Stefan de Konink wrote:
After partitioning with GPT, and formatting the NTFS disk under Windows
using 2K sectors per cluster size, I am unable to mount the partition
using ntfs-3g.
Unexpected sectors per cluster value (244).
Failed to mount '/dev/sdb1': Invalid argument
The device '/dev/sdb1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Is it as trivial as adding the extra values to libntfs-3g/bootsect.c?
Not exactly, because the new values do not fit into a byte.
I have posted a patch for that on Fedora bugzilla :
https://bugzilla.redhat.com/attachment.cgi?id=1433620
(attached to the bug report :
https://bugzilla.redhat.com/show_bug.cgi?id=1575227)
Note : the value 244 is related to the new biggest cluster
size (2MB). As the biggest block size for file transfers
in standard Linux configurations is 131K, using clusters
bigger than 131K will not be efficient. I would not
recommend using clusters bigger than 65K unless you have
a specific need.
Jean-Pierre
ntfs_log_debug("Checking sectors per cluster.\n");
switch (b->bpb.sectors_per_cluster) {
case 1: case 2: case 4: case 8: case 16: case 32: case 64: case 128:
break;
default:
ntfs_log_error("Unexpected sectors per cluster value (%d).\n",
b->bpb.sectors_per_cluster);
goto not_ntfs;
}
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
