Paweł Witas wrote 2012-04-11 23.12:
> Prefix "fusefs_" is 7 characters long, as well as "txantfs", even with
> two \0 *both* should fit in 16 characters.Now you're confusing things. 'fusefs_' is 7 characters but 'osxfusefs_'
is 10 characters. the string "osxfusefs_txantfs\0" is 19 characters.> Besides that, if there is an error message like "fstypename can be at
> most /%n characters.", you should inform the user what is the
> fstypename that causes this problem./
> /I had to modify this error message to /"fstypename %s can be at most
> /%n characters." to be able diagnose my problem. This is the
> difference between informative and meaningless error messages./
>
> There is nothing wrong in Tuxera NTFS 10.1 and I won't buy a new
> version, because I have already solved my problem.Here's a huge misunderstanding. There's no charge for updating to newer
versions with the license you have purchased. You can just download and
install it if you have bought a product key.> I understand that its authors had to shorten fstypename "txantfs" to
> make it compatible with OSXFUSE.No, see above. Tuxera NTFS for Mac 2010.1 was released a long time
before OSXFUSE was conceived.Regards,
- Erik
What version of TrueCrypt are you using? I did a quick test and mounting a container file containing an encrypted NTFS volume works out of the box for me using TrueCrypt 7.1a and OSXFUSE 2.3.9. I tested with NTFS-3G 2010.10.2 and Tuxera NTFS for Mac 2012.3.
Regards,
Benjamin
I'm using Hackintosh Hazard 10.6.8 (upgraded from 10.6.6), Tuxera NTFS 2010.1 and newest Truecrypt 7.1a. I checked on my laptop and desktop with OSXFuse modified to show filesystem type name in the error message.
My point is that the limit of only four characters for the filesystem type name is too small, maybe you are using another, shorter name than "txantfs" but there should be limit of 16 characters including \0, as stated in bsd/sys/mount.h, line 114 #define MFSTYPENAMELEN 16I don't know what OSXFUSE_FS_TYPE (=10) is, but it is certainly something different than MFSTYPENAMELEN. If you concatenate two strings, please make sure that there is enough space for the result provided.
And I've been trying to mount Truecrypt encrypted NTFS partitions, so I think that it is rather a problem with cooperation of Tuxera NTFS 2010.1 with OSXFuse, caused by this limit of 4 characters.
Am 10.04.2012 um 13:40 schrieb Paweł Witas:
I'm using Hackintosh Hazard 10.6.8 (upgraded from 10.6.6), Tuxera NTFS 2010.1 and newest Truecrypt 7.1a. I checked on my laptop and desktop with OSXFuse modified to show filesystem type name in the error message.
I can confirm the TrueCrypt 7.1a + OSXFUSE 2.3.9 + Tuxera NTFS for Mac 2012.3 work on Mac OS X 10.6. You are using a very outdated version of Tuxera's NTFS driver. Please install the latest version.
My point is that the limit of only four characters for the filesystem type name is too small, maybe you are using another, shorter name than "txantfs" but there should be limit of 16 characters including \0, as stated in bsd/sys/mount.h, line 114 #define MFSTYPENAMELEN 16I don't know what OSXFUSE_FS_TYPE (=10) is, but it is certainly something different than MFSTYPENAMELEN. If you concatenate two strings, please make sure that there is enough space for the result provided.
Please take a look at struct vfsstatfs in bsd/sys/mount.h.
struct vfsstatfs {uint32_t f_bsize; /* fundamental file system block size */size_t f_iosize; /* optimal transfer block size */uint64_t f_blocks; /* total data blocks in file system */uint64_t f_bfree; /* free blocks in fs */uint64_t f_bavail; /* free blocks avail to non-superuser */uint64_t f_bused; /* free blocks avail to non-superuser */uint64_t f_files; /* total file nodes in file system */uint64_t f_ffree; /* free file nodes in fs */fsid_t f_fsid; /* file system id */uid_t f_owner; /* user that mounted the filesystem */uint64_t f_flags; /* copy of mount exported flags */char f_fstypename[MFSTYPENAMELEN];/* fs type name inclus */char f_mntonname[MAXPATHLEN];/* directory on which mounted */char f_mntfromname[MAXPATHLEN];/* mounted filesystem */uint32_t f_fssubtype; /* fs sub-type (flavor) */void *f_reserved[2]; /* For future use == 0 */};
As you can see the f_fstypename field is limited to MFSTYPENAMELEN characters. You can't just increase that number. Your patch simply cuts off the last part of the type name. I'm not convinced that this is the right thing to do.
Am 10.04.2012 um 14:14 schrieb Paweł Witas:
And I've been trying to mount Truecrypt encrypted NTFS partitions, so I think that it is rather a problem with cooperation of Tuxera NTFS 2010.1 with OSXFuse, caused by this limit of 4 characters.
OSXFUSE has never been tested with this particular version of Tuxera's NTFS driver, at least not by me.
Now you're confusing things. 'fusefs_' is 7 characters but 'osxfusefs_'
is 10 characters. the string "osxfusefs_txantfs\0" is 19 characters.
> Besides that, if there is an error message like "fstypename can be at
> most /%n characters.", you should inform the user what is the
> fstypename that causes this problem./
> /I had to modify this error message to /"fstypename %s can be at most
> /%n characters." to be able diagnose my problem. This is the
> difference between informative and meaningless error messages./
>
> There is nothing wrong in Tuxera NTFS 10.1 and I won't buy a new
> version, because I have already solved my problem.
Here's a huge misunderstanding. There's no charge for updating to newer
versions with the license you have purchased. You can just download and
install it if you have bought a product key.
> I understand that its authors had to shorten fstypename "txantfs" to
> make it compatible with OSXFUSE.
No, see above. Tuxera NTFS for Mac 2010.1 was released a long time